[jira] [Commented] (SOLR-13411) CompositeIdRouter calculates wrong route hash if atomic update is used for route.field

["Eugene Tenkaev (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/SOLR-13411?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17042226#comment-17042226 ] 

Eugene Tenkaev commented on SOLR-13411:
---------------------------------------

Same here, it's a critical bug since it's routes document to the wrong shard which creates duplicates of documents on different shards.

To find this you need to go through code of Solr.

Why it's not solved so far?

> 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
>            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
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@lucene.apache.org
For additional commands, e-mail: issues-help@lucene.apache.org