This is fixed. My SolrJ client was putting a JSON object into a multivalued field in the SolrInputDocument. Solr returned a 0 status code but did not add the bad object, instead it performed what looks like an atomic index as described above. Once I removed the illegal JSON object from the SolrInputDocument a regular document replacement occurred and my unwanted fields were removed in Solr.
Is this a known behaviour, for Solr to switch into atomic update mode based on attributes of the SolrInputDocument? -- View this message in context: http://lucene.472066.n3.nabble.com/Reindex-of-document-leaves-old-fields-behind-tp4206710p4207164.html Sent from the Solr - User mailing list archive at Nabble.com.
