Sigh, user error. I missed this in the 4.1 release notes:
Collections that do not specify numShards at collection creation time use custom sharding and default to the "implicit" router. Document updates received by a shard will be indexed to that shard, unless a "*shard*" parameter or document field names a different shard. On Fri, Mar 22, 2013 at 3:39 PM, Gary Yngve <gary.yn...@gmail.com> wrote: > I have a situation we just discovered in solr4.2 where there are > previously cached results from a limited field list, and when querying for > the whole field list, it responds differently depending on which shard gets > the query (no extra replicas). It either returns the document on the > limited field list or the full field list. > > We're releasing tonight, so is there a query param to selectively bypass > the cache, which I can use as a temp fix? > > Thanks, > Gary >
