[
https://issues.apache.org/jira/browse/SOLR-5017?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13704547#comment-13704547
]
Noble Paul commented on SOLR-5017:
----------------------------------
bq.Do you have such a system? .....
Yes. I had . The entire Aol mail system already has billions of documents where
id is immutable and referenced in code. While I was there I hacked solr to a
field based sharding scheme. A lot of users will not have that expertise or
patience
bq.Don't really know, I've been meaning to dive into that patch but haven't.
IIRC , SolJ consults the DocRouter to identify the target slice/leader .If
future patches need it they too should.
bq.But I fear at this point that having two ways of routing things around
We already have multiple ways of routing things after SOLR-4221 is in place
(next release will have it . Custom Sharding does not have a 'mangled id'
concept as of now. It is not going to impact anyone who is already using the
current scheme with compositeId. You will need to create your cluster
explicitly with that option (which will be new users) . We will solve any
problems as we go along
bq.Premature optimization?
This is not optimization. I'm just trying to be intuitive and user-friendly .
AFAIK Almost all nosql systems do grouping on the basis of some field value .
bq.what happens when a document is updated and the value of this field changes?
Good question. It should be dealt in exactly the same way 'id' updates are
handled today
> 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
