Jeff, I believe the shards.qt parameter is what you're looking for. For example when using the "/elevate" handler with SolrCloud I use the following url to tell Solr to use the "/elevate" handler on the shards:
http://localhost:8983/solr/collection1/elevate?q=ipod&wt=json&indent=true&shards.qt=/elevate Joel Bernstein Search Engineer at Heliosearch On Tue, Feb 11, 2014 at 1:01 PM, Jeff Wartes <jwar...@whitepages.com> wrote: > > Got it in one. Thanks! > > > On 2/11/14, 9:50 AM, "Shawn Heisey" <s...@elyograg.org> wrote: > > >On 2/11/2014 10:21 AM, Jeff Wartes wrote: > >> I¹m working on a port of a Solr service to SolrCloud. (Targeting v4.6.0 > >>at present.) The old query style relied on using /solr/select?qt=foo to > >>select the proper requestHandler. I know handleSelect=true is deprecated > >>now, but it¹d be pretty handy for testing to be able to be backwards > >>compatible, at least until some time after the initial release. > >> > >> So in my SolrCloud configuration, I set <requestDispatcher > >>handleSelect="true²> and deleted the /select requestHandler as suggested > >>here: > >> > http://wiki.apache.org/solr/SolrRequestHandler#Old_handleSelect.3Dtrue_Re > >>solution_.28qt_param.29 > >> > >> However, my /solr/collection1/select?qt=foo query throws an ³unknown > >>handler: null² error with this configuration. Has anyone successfully > >>tried handleSelect=true with the collections api? > > > >I'm pretty sure that if you won't have a handler named /select, then you > >need to have default="true" as an attribute on one of your other handler > >definitions. > > > >See line 715 of the example solrconfig.xml for Solr 3.5: > > > > > http://svn.apache.org/viewvc/lucene/dev/branches/lucene_solr_3_5/solr/exam > >ple/solr/conf/solrconfig.xml?view=annotate > > > >Thanks, > >Shawn > > > >
