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
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
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
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=ipodwt=jsonindent=trueshards.qt=/elevate
]
Sent: Tuesday, February 11, 2014 3:11 PM
To: solr-user@lucene.apache.org
Subject: Re: handleSelect=true with SolrCloud
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
