[
https://issues.apache.org/jira/browse/SOLR-13081?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16824141#comment-16824141
]
Munendra S N commented on SOLR-13081:
-------------------------------------
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?
Is there any particular reason to change *computeInPlaceUpdatableFields* method
from static to non-static? This method has access to *AddUpdateCommand* which
in turn has access to SolrQueryRequest. So, should be possible to get routeField
Except this static to non-static change, other changes LGTM
> 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: [email protected]
For additional commands, e-mail: [email protected]
