[
https://issues.apache.org/jira/browse/SOLR-6311?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14085258#comment-14085258
]
Yonik Seeley commented on SOLR-6311:
------------------------------------
bq. When performing distributed searches, you have to specify shards.qt unless
you're on the default /select path for your handler.
This was by design, and we should consider very carefully before changing it.
Most of the time, other handlers were used to add default parameters. When
this is the case, it's preferable to hit a bare /select handler for
sub-requests as hitting the same handler again and adding defaults again will
have a lot of side effects and sometimes produce incorrect distributed results.
The worst is when a handler specifies shards or something, and this causes an
endless loop.
> SearchHandler should use path when no qt or shard.qt parameter is specified
> ---------------------------------------------------------------------------
>
> Key: SOLR-6311
> URL: https://issues.apache.org/jira/browse/SOLR-6311
> Project: Solr
> Issue Type: Bug
> Affects Versions: 4.9
> Reporter: Steve Molloy
> Attachments: SOLR-6311.patch
>
>
> When performing distributed searches, you have to specify shards.qt unless
> you're on the default /select path for your handler. As this is configurable,
> even the default search handler could be on another path. The shard requests
> should thus default to the path if no shards.qt was specified.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
