You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@lucene.apache.org by "Ivan Djurasevic (Jira)" <ji...@apache.org> on 2020/07/06 20:11:00 UTC
[jira] [Commented] (SOLR-14631) Can't perform atomic update if
document doesn't exists in collection
[ https://issues.apache.org/jira/browse/SOLR-14631?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17152288#comment-17152288 ]
Ivan Djurasevic commented on SOLR-14631:
----------------------------------------
Thanks [~erickerickson] for quick response. In this case, DistributedUpdateProcessor should't throw exception, it should add document as new(that is how is working on version 5).
> Can't perform atomic update if document doesn't exists in collection
> --------------------------------------------------------------------
>
> Key: SOLR-14631
> URL: https://issues.apache.org/jira/browse/SOLR-14631
> Project: Solr
> Issue Type: Bug
> Security Level: Public(Default Security Level. Issues are Public)
> Components: update, UpdateRequestProcessors
> Affects Versions: 8.5, 8.5.1, 8.5.2
> Reporter: Ivan Djurasevic
> Priority: Major
>
> If client try to perform atomic update on document which doesn't exists and query params contain _route_ param, DistributedUpdateProcessor throws next exception:
> throw new SolrException(ErrorCode.BAD_REQUEST,
> "Could not find document id=" + idString +
> ", perhaps the wrong \"_route_\" param was supplied");
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@lucene.apache.org
For additional commands, e-mail: issues-help@lucene.apache.org