You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Mikhail Khludnev (JIRA)" <ji...@apache.org> on 2018/12/18 16:05:00 UTC
[jira] [Comment Edited] (SOLR-13081) In-Place Update doesn't work
when route.field is defined
[ https://issues.apache.org/jira/browse/SOLR-13081?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16724198#comment-16724198 ]
Mikhail Khludnev edited comment on SOLR-13081 at 12/18/18 4:04 PM:
-------------------------------------------------------------------
It makes sense to me. I worry where we can commit public method changes. I appreciate a review by other pair of eyes, I'll take care about commit.
was (Author: mkhludnev):
It make sense to me. I worry where we can commit public method changes. I appreciate a review by other pair of eyes, I'll take care about commit.
> 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
>
>
> 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-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org