I am not sure if optimistic concurrency would help in deduplicating but yes, as Shalin points out, you'll be able to spot issues with your client code.
On Wed, Oct 30, 2013 at 4:18 PM, Shalin Shekhar Mangar < shalinman...@gmail.com> wrote: > Perhaps you are running the update request more than once accidentally? > > Can you try using optimistic update with _version_ while sending the > update? This way, if some part of your code is making a duplicate request > then Solr would throw an error. > > See > > https://cwiki.apache.org/confluence/display/solr/Updating+Parts+of+Documents > > > On Wed, Oct 30, 2013 at 3:35 PM, Anupam Bhattacharya <anupam...@gmail.com > >wrote: > > > I am working on a offline tagging capability to tag records with a > > thesaurus dictionary of key concepts. I am able to use the update="add" > > option using xml and json update calls for a field to update specific > > document field information. Although if I run the same atomic update > query > > twice then the multivalued string fields start showing duplicate value in > > the multivalued field. > > e.g. for a field name as tag at the initial it was having copper, iron, > > steel > > After running the atomic update query with <field name="tag" > > update="add">steel</field> I will get the tag field values as following: > > copper, iron, steel, steel. (Thus steel get added twice). > > I looked at RemoveDuplicatesTokenFilterFactory but it helps to remove > token > > duplicate not multivalued field duplicates. Is there any updateProcessor > to > > stop the incoming duplicate value from indexing ? > > > > Thanks in advance for any help. > > > > Regards > > Anupam > > > > > > -- > Regards, > Shalin Shekhar Mangar. > -- Anshum Gupta http://www.anshumgupta.net
