[
https://issues.apache.org/jira/browse/SOLR-17397?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17873475#comment-17873475
]
Tim Owen commented on SOLR-17397:
---------------------------------
Thanks Eric and David for prompt reviewing! I have had a quick look through
other update processors, although I think the main times you have to consider
child documents is when dealing with atomic updates, and not many resource
processors do.
> 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
> Assignee: Eric Pugh
> Priority: Minor
> Labels: pull-request-available
> Fix For: 9.8
>
> Time Spent: 2h
> 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]
