[
https://issues.apache.org/jira/browse/SOLR-5017?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13704506#comment-13704506
]
Jack Krupansky commented on SOLR-5017:
--------------------------------------
bq. there's no case made for why this is a better thing than using the current
! syntax
Logically, I think it makes perfect sense to be able to declare what field
should be used for "grouping" of documents, and that some apps want more of a
functional grouping (e.g., by department or product category.) Having to
manually (and forever) muck up the ID field values for routing always seemed
rather odd to me. Maybe the latter has some utility on its own, but the former
seems more sensible to me.
And, then there is the issue of how to change the shard of an existing document
that was, in terms I use, "explicitly routed", using the "!" notation. I mean,
if the ID of that document is referenced in other documents, all of those other
documents would need to be manually updated as well. Before the introduction of
the "!" notation, key values were completely application controlled, but with
"!", suddenly Solr interjects itself into the ID generation process. Some
day... even Data Import Handler users are going to start flooding the Solr-user
email list with questions about how to set and change routing and why key
values containing "!" seem to be causing SolrCloud to be distributing documents
to shards in an unexpected manner (because they didn't know about the "!"
notation.)
> 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
