I don't know what I have to do to use the atomic update feature but I am not aware of using it. But the way you describe it, it means that the copyField directive does not overwrite the existing field content and that's an easy explanation to what is happening in my case. Then the second update (which I do manually, i.e. read current state, manipulate fields and then add the document with the same id) will lead to this. That was not so obvious to me from the docs.
Thanks, Robert On Thu, Jun 6, 2013 at 12:18 AM, Chris Hostetter <hossman_luc...@fucit.org> wrote: > > : I updated the Index using SolrJ and got the exact same error message > > there aren't a lot of specifics provided in this thread, so this may not > be applicable, but if you mean you actaully using the "atomic updates" > feature to update an existing document then the problem is that you still > have the existing value in your name2 field, as well as another copy of > the "name" field evaluated by copyField after the updates are applied... > > http://wiki.apache.org/solr/Atomic_Updates#Stored_Values > > > -Hoss
