[
https://issues.apache.org/jira/browse/SOLR-14631?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Erick Erickson resolved SOLR-14631.
-----------------------------------
Resolution: Fixed
Please raise questions like this on the user's list, we try to reserve JIRAs
for known bugs/enhancements rather than usage questions.
See:
http://lucene.apache.org/solr/community.html#mailing-lists-irc there are links
to both Lucene and Solr mailing lists there.
A _lot_ more people will see your question on that list and may be able to help
more quickly.
If it's determined that this really is a code issue or enhancement to Lucene or
Solr and not a configuration/usage problem, we can raise a new JIRA or reopen
this one.
In this case, atomic update is intended to work, well, on existing documents.
It has to pull the data from the existing doc, overlay the updates and then
re-index it.
> 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-unsubscr...@lucene.apache.org
For additional commands, e-mail: issues-h...@lucene.apache.org
