Niko Himanen created SOLR-13411:
-----------------------------------
Summary: 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
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: [email protected]
For additional commands, e-mail: [email protected]
