Hi Dmitry (you may not want to additionally copy Yonik, he's subscribed to this list, too)
It sounds like you have the knowledge of which query maps to which shard. If so, why not control/change the value of "shards" param in the request to your front-end Solr (aka distributed request dispatcher) within your app, which is the one calling Solr? Otis ---- Sematext :: http://sematext.com/ :: Solr - Lucene - Nutch Lucene ecosystem search :: http://search-lucene.com/ ----- Original Message ---- > From: Dmitry Kan <dmitry....@gmail.com> > To: solr-user@lucene.apache.org; yo...@lucidimagination.com > Sent: Thu, June 2, 2011 7:00:53 AM > Subject: query routing with shards > > Hello all, > > We have currently several pretty fat logically isolated shards with the same > schema / solrconfig (indices are separate). We currently have one single > front end SOLR (1.4) for the client code calls. Since a client code query > usually hits only one shard, we are considering making a smart routing of > queries to the shards they map to. Can you please give some pointers as to > what would be an optimal way to achieve such a routing inside the front end > solr? Is there a way to configure mapping inside the solrconfig? > > Thanks. > > -- > Regards, > > Dmitry Kan >
