You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "mosh (JIRA)" <ji...@apache.org> on 2018/08/08 05:31:00 UTC
[jira] [Comment Edited] (SOLR-12638) Provide a simple API to update
block (update child documents)
[ https://issues.apache.org/jira/browse/SOLR-12638?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16572699#comment-16572699 ]
mosh edited comment on SOLR-12638 at 8/8/18 5:30 AM:
-----------------------------------------------------
This is currently just a small initial proposal.
when a user wants to update a document inside a block (has _ROOT_ field), these procedures are to run:
* Child document transformer could run and rebuild the current block(prior update) as a SolrInputDocument
* Documents that need be updated are to be swapped with their newer counter parts
* Perhaps use AtomicUpdate or some other URP to index the new block, while deleting the old one using a delete query of _ROOT_:rootID.
WDYT?
was (Author: moshebla):
This is currently just a small initial proposal.
when a user wants to update a document inside a block (has _ROOT_ field), these procedures are to run:
Child document transformer could run and rebuild the current block(prior update) as a SolrInputDocument
* Documents that need be updated are to be swapped with their newer counter parts
* Perhaps use AtomicUpdate or some other URP to index the new block, while deleting the old one using a delete query of _ROOT_:rootID.
WDYT?
> Provide a simple API to update block (update child documents)
> -------------------------------------------------------------
>
> Key: SOLR-12638
> URL: https://issues.apache.org/jira/browse/SOLR-12638
> Project: Solr
> Issue Type: Sub-task
> Security Level: Public(Default Security Level. Issues are Public)
> Reporter: mosh
> Priority: Major
>
> I have been toying with the thought of using this transformer in conjunction with NestedUpdateProcessor and AtomicUpdate to allow SOLR to completely re-index the entire nested structure. This is just a thought, I am still thinking about implementation details. Hopefully I will be able to post a more concrete proposal soon.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org