[ https://issues.apache.org/jira/browse/SOLR-9530?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16021392#comment-16021392 ]
ASF subversion and git services commented on SOLR-9530: ------------------------------------------------------- Commit 31e02e93a5712d8fa2cafff3b13ce329563c6579 in lucene-solr's branch refs/heads/master from [~ctargett] [ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=31e02e9 ] Ref Guide: fix note for atomic updates after SOLR-9530 > 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 > Assignee: Noble Paul > Fix For: 6.6, master (7.0) > > Attachments: assertU(...)-works.png, commit()-doesn't-work.png, > SOLR-9530.patch, SOLR-9530.patch, SOLR-9530.patch, SOLR-9530.patch, > SOLR-9530.patch, SOLR-9530.patch, SOLR-9530.patch, SOLR-9530.patch, > SOLR-9530.patch, SOLR-9530.patch, SOLR-9530.patch, 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? > 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