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.
