[
https://issues.apache.org/jira/browse/SOLR-5320?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13796627#comment-13796627
]
Anshum Gupta commented on SOLR-5320:
------------------------------------
Adding to that, if the user wants to override the default numBits, everything
would be borrowed/lent back to the document id component i.e. the 3rd component
(c in the example below).
e.g. : a!b!c
> Multi level compositeId router
> ------------------------------
>
> Key: SOLR-5320
> URL: https://issues.apache.org/jira/browse/SOLR-5320
> Project: Solr
> Issue Type: New Feature
> Components: SolrCloud
> Reporter: Anshum Gupta
> Original Estimate: 336h
> Remaining Estimate: 336h
>
> This would enable multi level routing as compared to the 2 level routing
> available as of now. On the usage bit, here's an example:
> Document Id: myapp!dummyuser!doc
> myapp!dummyuser! can be used as the shardkey for searching content for
> dummyuser.
> myapp! can be used for searching across all users of myapp.
> I am looking at either a 3 (or 4) level routing. The 32 bit hash would then
> comprise of 8X4 components from each part (in case of 4 level).
--
This message was sent by Atlassian JIRA
(v6.1#6144)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]