[
https://issues.apache.org/jira/browse/SOLR-5017?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13703653#comment-13703653
]
Yonik Seeley commented on SOLR-5017:
------------------------------------
bq. the _shard_ parameter is the actual name of the shard.
For the implicit router. For a hash based router, it should be the value that
is hashed to then lookup the shard based on ranges.
bq. In case of compositeId router , I would like to read the part before the
(!) to be read from the 'shardField'.
I think it should work simpler... _shard_ is used as the whole value to hash on
for any hash based router.
It's simple - if you want to have doc B have the exact same hash as doc A, then
you give _shard_=A when adding doc B.
bq. I would like to read the part before the (!) to be read from the
'shardField'.
Perhaps that should be a different router... compositeField rather than
compositeId.
> Allow sharding based on the value of a field
> --------------------------------------------
>
> Key: SOLR-5017
> URL: https://issues.apache.org/jira/browse/SOLR-5017
> Project: Solr
> Issue Type: Sub-task
> Reporter: Noble Paul
> Assignee: Noble Paul
>
> We should be able to create a collection where sharding is done based on the
> value of a given field
> collections can be created with shardField=fieldName, which will be persisted
> in DocCollection in ZK
> implicit DocRouter would look at this field instead of _shard_ field
> CompositeIdDocRouter can also use this field instead of looking at the id
> field.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
