Well, let's see the code. Standard updates should replace the previous docs, reindexing the same unique ID with fewer fields should show fewer fields. So something's weird here.
Although do, just for yucks, issue a query on some of the unique ids in question, I'd be curious if you get more than one back which would tell us something. Did you push your schema up to Zookeeper and reload (or restart) your collection before re-indexing things? And are you sure the documents are actually getting indexed and that the update is succeeding? (check your Solr logs probably here). Best, Erick On Wed, May 20, 2015 at 5:12 PM, tuxedomoon <dancolem...@yahoo.com> wrote: > The uniqueKey value is the same. > > The new documents contain fewer fields than the already indexed ones. Could > this cause the updates to be treated as atomic? With the persisting fields > treated as un-updated? > > Routing should be implicit since the collection was created using numShards. > Many request for the same document with cache busting produce the same > unwanted fields, so I doubt the "correct" one is hiding somewhere. I can > also see the timestamp going up with each reindex. > > > > > -- > View this message in context: > http://lucene.472066.n3.nabble.com/Reindex-of-document-leaves-old-fields-behind-tp4206710p4206732.html > Sent from the Solr - User mailing list archive at Nabble.com.
