lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Noble Paul (JIRA)" <>
Subject [jira] [Commented] (SOLR-5017) Allow sharding based on the value of a field
Date Tue, 09 Jul 2013 08:09:48 GMT


Noble Paul commented on SOLR-5017:

bq.I could see by default, the compositeId router also paying attention to the _shard_ parameter

the _shard_ parameter is the actual name of the shard. In case of compositeId router , the
client is agnostic of the shard name and all that it cares about is shard.keys. What I mean
to say is, the name _shard_ can be a bit confusing

As of now we don't have a plan on how to do shard splitting for 'implicit' router. Let's keep
it as  TBD

In case of compositeId router , I would like to read the part before the (!) to be read from
the 'shardField'. The semantics will be exactly same as it is now. Reading the value from
a request parameter would mean we will need to persist it along with the document in some
field . 
> Allow sharding based on the value of a field
> --------------------------------------------
>                 Key: SOLR-5017
>                 URL:
>             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:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message