[
https://issues.apache.org/jira/browse/SOLR-13411?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17046539#comment-17046539
]
ASF subversion and git services commented on SOLR-13411:
--------------------------------------------------------
Commit 3befb8be941afb0f6e5bdf757ceda631291e5f60 in lucene-solr's branch
refs/heads/master from Mikhail Khludnev
[ https://gitbox.apache.org/repos/asf?p=lucene-solr.git;h=3befb8b ]
SOLR-13411: reject incremental update for route.field, uniqueKey and
_version_.
> CompositeIdRouter calculates wrong route hash if atomic update is used for
> route.field
> --------------------------------------------------------------------------------------
>
> Key: SOLR-13411
> URL: https://issues.apache.org/jira/browse/SOLR-13411
> Project: Solr
> Issue Type: Bug
> Components: SolrCloud
> Affects Versions: 7.5
> Reporter: Niko Himanen
> Assignee: Mikhail Khludnev
> Priority: Minor
> Attachments: SOLR-13411.patch, SOLR-13411.patch
>
>
> If collection is created with router.field -parameter to define some other
> field than uniqueField as route field and document update comes containing
> route field updated using atomic update syntax (for example set=123), hash
> for document routing is calculated from "set=123" and not from 123 which is
> the real value which may lead into routing document to wrong shard.
>
> This happens in CompositeIdRouter#sliceHash, where field value is used as is
> for hash calculation.
>
> I think there are two possible solutions to fix this:
> a) Allow use of atomic update also for route.field, but use real value
> instead of atomic update syntax to route document into right shard.
> b) Deny atomic update for route.field and throw exception.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]