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 2019/04/18 11:54:00 UTC
[jira] [Commented] (SOLR-13411) CompositeIdRouter calculates wrong
route hash if atomic update is used for route.field
[ https://issues.apache.org/jira/browse/SOLR-13411?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16820999#comment-16820999 ]
Mikhail Khludnev commented on SOLR-13411:
-----------------------------------------
Isn't is a dupe of SOLR-13081?
> 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
> Security Level: Public(Default Security Level. Issues are Public)
> Components: SolrCloud
> Affects Versions: 7.5
> Reporter: Niko Himanen
> Priority: Minor
>
> 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
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org