[
https://issues.apache.org/jira/browse/SOLR-5017?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13704595#comment-13704595
]
Yonik Seeley commented on SOLR-5017:
------------------------------------
bq. > Perhaps that should be a different router... compositeField rather than
compositeId.
bq. Too many routers can be confusing to users.
Heh - my favorite argument. "confusing to users" can be trotted out in any
context ;-)
Too many options can be just as confusing... 3 routers with 5 options each vs 5
routers with 3 or whatever. Let's talk about the *best* option. If we have a
good default and good documentation, confusion shouldn't enter the equation.
As far as compositeId router goes, I'm not sure I care if we create a new
compositeField router or if we add more parameters / functionality to
compositeId. Giving the exact same \_shard\_ parameter should give the exact
same hash code though - it shouldn't just be the first part of a composite id.
> 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
