[
https://issues.apache.org/jira/browse/SOLR-6472?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14119076#comment-14119076
]
Yonik Seeley commented on SOLR-6472:
------------------------------------
bq. I understand that but I am not sure what kind of use-cases would require
routing by a plain id?
Neither am I, but it seems like a better idea to enable use-cases we haven't
thought about yet (unless the downsides of doing so are substantial enough of
course).
Off the top of my head, one is doing a commit (to ensure visibility to search)
of a specific document.
Also, perhaps use-cases where one wants to co-locate one document with
another... one would want to specify that via the full id of the document (and
not have "!" appended automatically).
> Don't require an '!' character at the end of a _route_ (shard.keys) value
> -------------------------------------------------------------------------
>
> Key: SOLR-6472
> URL: https://issues.apache.org/jira/browse/SOLR-6472
> Project: Solr
> Issue Type: Improvement
> Components: SolrCloud
> Reporter: Shalin Shekhar Mangar
> Priority: Minor
> Labels: SolrCloud, difficulty-easy, impact-low
> Fix For: 4.11
>
> Original Estimate: 4h
> Remaining Estimate: 4h
>
> A routing key can be specified in the "_route_" parameter which is then
> hashed and the shard corresponding to the key is selected for
> querying/indexing. But we require users to specify an exclamation mark at the
> end to get the right routing otherwise it fails silently or gives the wrong
> hash. This also applies to the split.key param used in shard splitting.
> This is really annoying because you can forget to add the '!' character at
> the end and you wouldn't even know why the request was routed incorrectly.
> We should make the '!' character optional and support keys both with and
> without it.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
