[
https://issues.apache.org/jira/browse/SOLR-17397?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17872331#comment-17872331
]
Eric Pugh commented on SOLR-17397:
----------------------------------
I appreciate the attention to child docs, which often get skipped over! Out
of curiosity, do you think that other update processors also suffer similar
issues? Just wondering if there needs to be a more global review of all the
update processes to ensure they work well with child docs???
> Skip atomic updates for non-existent child documents
> ----------------------------------------------------
>
> Key: SOLR-17397
> URL: https://issues.apache.org/jira/browse/SOLR-17397
> Project: Solr
> Issue Type: Improvement
> Security Level: Public(Default Security Level. Issues are Public)
> Components: UpdateRequestProcessors
> Reporter: Tim Owen
> Priority: Minor
> Labels: pull-request-available
> Time Spent: 20m
> Remaining Estimate: 0h
>
> We have an update processor that allows skipping updates for non-existent
> documents, {{SkipExistingDocumentsUpdateProcessor}} but this does not
> currently handle atomic updates to child documents. So the update is passed
> through and then fails because {{AtomicUpdateDocumentMerger}} throws an
> exception if it cannot find the child document (leading to a 500 response
> from Solr)
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
