: The documentation int the Collections API says "The value can be ... : *implicit*, which uses an internal default hash". : I think most people would assume the "hash" would be used to route the : data. : Meanwhile the description of CompositID in the "Document Routing" section : only discusses how modify your document IDs, which I did not want to do.
Hmmm... I'm guessing you are looking at PDF copy of the ref guide? Pretty sure that was a mistake that's already been fixed. At the moment the Collections API CREATE command says... https://cwiki.apache.org/confluence/display/solr/Collections+API "The 'implicit' router does not automatically route documents to different shards. Whichever shard you indicate on the indexing request (or within each document) will be used as the destination for those documents" And the details on document routing say... https://cwiki.apache.org/confluence/display/solr/Shards+and+Indexing+Data+in+SolrCloud#ShardsandIndexingDatainSolrCloud-DocumentRouting If you created the collection and defined the "implicit" router at the time of creation, you can additionally define a router.field parameter to use a field from each document to identify a shard where the document belongs. If the field specified is missing in the document, however, the document will be rejected. You could also use the _route_ parameter to name a specific shard. ...which i believe is all accurate. -Hoss http://www.lucidworks.com/