Yeah, shards.qt is the way to go.
I think this basically done because of a limitation around early distrib search.
If you want to do a distrib search against a bunch of shards and you put the
shards to search into the request handler, you then don't want to hit that same
request handler on the
On 1/18/2013 1:20 PM, Mike Schultz wrote:
Can someone explain the logic of not sending the qt parameter down to the
shards?
I see from here that qt is handled as a special case for ResultGrouping:
http://lucidworks.lucidimagination.com/display/solr/Result+Grouping
where there is a special shard.
Can someone explain the logic of not sending the qt parameter down to the
shards?
I see from here that qt is handled as a special case for ResultGrouping:
http://lucidworks.lucidimagination.com/display/solr/Result+Grouping
where there is a special shard.qt parameter.
in 3.x solrconfig.xml support
