[ https://issues.apache.org/jira/browse/SOLR-9530?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15879998#comment-15879998 ]
Ishan Chattopadhyaya commented on SOLR-9530: -------------------------------------------- bq. In case of multiple threads try to update the incoming doc to atomic-type update doc, all the threads will end up forming same atomic-type update doc (as same set of operations will be performed by 'SET' field). The problem is with "inc" operations. When two clients see the value to be, say 100, and want to increase by 50, they can supply the document version along with "inc":50. One of them would be executed first, and the second one would be rejected since the document version is no longer the same as what this client saw. Also, do consider the cases when one client is indexing without this URP, but another client is using this URP, both in parallel. > Add an Atomic Update Processor > ------------------------------- > > Key: SOLR-9530 > URL: https://issues.apache.org/jira/browse/SOLR-9530 > Project: Solr > Issue Type: New Feature > Security Level: Public(Default Security Level. Issues are Public) > Reporter: Varun Thacker > Attachments: SOLR-9530.patch, SOLR-9530.patch, SOLR-9530.patch > > > I'd like to explore the idea of adding a new update processor to help ingest > partial updates. > Example use-case - There are two datasets with a common id field. How can I > merge both of them at index time? > Proposed Solution: > {code} > <updateRequestProcessorChain name="atomic"> > <processor class="solr.processor.AtomicUpdateProcessorFactory"> > <str name="my_new_field">add</str> > </processor> > <processor class="solr.LogUpdateProcessorFactory" /> > <processor class="solr.RunUpdateProcessorFactory" /> > </updateRequestProcessorChain> > {code} > So the first JSON dump could be ingested against > {{http://localhost:8983/solr/gettingstarted/update/json}} > And then the second JSON could be ingested against > {{http://localhost:8983/solr/gettingstarted/update/json?processor=atomic}} > The Atomic Update Processor could support all the atomic update operations > currently supported. -- This message was sent by Atlassian JIRA (v6.3.15#6346) --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org