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 supports defining a list of SearchComponents on handler by handler basis. This flexibility goes away if qt isn't passed down or am I missing something? I'm using: <requestDispatcher handleSelect="true> for the legacy behavior. We want to be able to have a single endpoint (e.g. http://localhost:8983/solr/select) and modify query processing by varying only the query parameters. -- View this message in context: http://lucene.472066.n3.nabble.com/Solr-4-0-doesn-t-send-qt-parameter-to-shards-tp4034653.html Sent from the Solr - User mailing list archive at Nabble.com.
