[
https://issues.apache.org/jira/browse/SOLR-5017?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13704561#comment-13704561
]
Yonik Seeley commented on SOLR-5017:
------------------------------------
bq. It is very confusing to have these names behaving differently in different
routers.
Not sure I understand... we should definitely have the same parameters behaving
in the same way across all the routers.
\_shard\_ should work across all routers. I understand the naming issue
though... (the fact that _shard_ is just the input to the router, not the
actual shard name unless you're using the implicit router). \_shard\_ hasn't
even really been documented yet I don't think... it's possible we could change
it to \_routing\_ or \_route\_
bq. Should we rather not use the other parameter \'shard.keys across router
names , query and update requests .
I think we should use the same parameter name for query requests too (i.e.
deprecate "shard.keys")
> 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
