Hi, I'm also interested. When using composite the ID, the _route_ information is not kept on the document itself, so to me it looks like it's not possible as the split API <https://cwiki.apache.org/confluence/display/solr/Collections+API#CollectionsAPI-api3> doesn't have a relevant parameter to split correctly. Could report back once I try it in practice.
On Mon, Nov 10, 2014 at 7:27 PM, Ian Rose <ianr...@fullstory.com> wrote: > Howdy - > > We are using composite IDs of the form <user>!<event>. This ensures that > all events for a user are stored in the same shard. > > I'm assuming from the description of how composite ID routing works, that > if you split a shard the "split point" of the hash range for that shard is > chosen to maintain the invariant that all documents that share a routing > prefix (before the "!") will still map to the same (new) shard. Is that > accurate? > > A naive shard-split implementation (e.g. that chose the hash range split > point arbitrarily) could end up with "child" shards that split a routing > prefix. > > Thanks, > Ian >
