[
https://issues.apache.org/jira/browse/SOLR-5017?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13702659#comment-13702659
]
Yonik Seeley commented on SOLR-5017:
------------------------------------
bq. CompositeIdDocRouter can also use this field instead of looking at the id
field.
Agree - I could see by default, the compositeId router also paying attention to
the \_shard\_ parameter (as the implicit router does).
Even if the implicit router is configured to pay attention to a field other
than \_shard\_ in the document, it should still use _shard_ when looking at
query parameters.
This has some downsides thought too - related to splits and how to calculate
the has (store the _shard_ param when explicitly specified as a column? store
the calculated hash as a column?)
bq. Does this proposal eliminate the need to do explicit routing in the key
values?
Not sure what you mean by "explicit routing" but if you mean the compositeId
stuff, no. That has a lot of benefits and will remain the default.
> 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: [email protected]
For additional commands, e-mail: [email protected]
