[jira] [Commented] (SOLR-6311) SearchHandler should use path when no qt or shard.qt parameter is specified

["Timothy Potter (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/SOLR-6311?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14314389#comment-14314389 ] 

Timothy Potter commented on SOLR-6311:
--------------------------------------

Same issue I stumbled upon trying to fix SOLR-4479.

bq. Most of the time, other handlers were used to add default parameters.

True, but sometimes they also add search components so silently routing shard requests to {{/select}} is just plain wrong.

Seems like maybe the the hook to determine if the path should be applied as the default for {{shards.qt}} is whether there are custom components defined on that instance of SearchHandler? Seems a little nuanced but better for new users than the current experience.

> 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.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org