Thanks Shawn, that fixed it ! 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.
thanks again, .strick On Tue, Oct 6, 2015 at 8:15 AM, Shawn Heisey <apa...@elyograg.org> wrote: > On 10/6/2015 7:58 AM, Steve wrote: > > I’ve been unable to get solrcloud to distribute data across 4 solr nodes > > with the “route.name=implicit” feature of the collections API. > > > > The nodes are live, and the graphs are green. All the data (the “Films” > > example data) shows up on one node, the node that received the CREATE > > command. > > A better name for the implicit router is "manual." The implicit router > doesn't actually route. It assumes that you know what you are doing and > have sent the request to the shard where you want it to be indexed. > > You want the compositeId router. > > Even though the name "implicit" makes sense in the context of Solr > *code*, it is a confusing name when it comes to user expectations. > You're not the first one to be confused by this, which is why I opened > this issue: > > https://issues.apache.org/jira/browse/SOLR-6630 > > Thanks, > Shawn > >
