[
https://issues.apache.org/jira/browse/SOLR-13081?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16824174#comment-16824174
]
Munendra S N commented on SOLR-13081:
-------------------------------------
{quote}Please correct me if I'm wrong, this change is only for implicit routing
since for compositeId, routing info is prefix of id, it should already be
working. Is this understanding correct?{quote}
*Update:* For compositeId, inplace would have worked if explicit router field
was not set, in that case id would be used and there is already a check on id.
Support for adding explicit router field for compositeId was added in
SOLR-5017. I think
[documentation|https://lucene.apache.org/solr/guide/7_7/shards-and-indexing-data-in-solrcloud.html#document-routing]
is not updated about this change
> In-Place Update doesn't work when route.field is defined
> --------------------------------------------------------
>
> Key: SOLR-13081
> URL: https://issues.apache.org/jira/browse/SOLR-13081
> Project: Solr
> Issue Type: Bug
> Security Level: Public(Default Security Level. Issues are Public)
> Components: update
> Reporter: Dr Oleg Savrasov
> Priority: Major
> Attachments: SOLR-13081.patch, SOLR-13081.patch, SOLR-13081.patch
>
>
> As soon as cloud collection is configured with route.field property, In-Place
> Updates are not applied anymore. This happens because
> AtomicUpdateDocumentMerger skips only id and version fields and doesn't
> verify configured route.field.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
