[
https://issues.apache.org/jira/browse/SOLR-6311?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14314547#comment-14314547
]
Hoss Man commented on SOLR-6311:
--------------------------------
doesn't the initParam stuff noble added improve the situation with vanity
handler paths that have defaults? and doesn't it play nice with distibuted
requests? (so that it only adds the defaults on the initial request, not the
per-shard requests -- if not it should)
i think we should just bite the bullet on making the switch...
straw man:
* make behavior conditional on LUCENE_MATCH_VERSION
** if < X, shards.qt defaults to /select
** if > X, shards.qt defaults to current handler
* users who want to upgrade LUCENE_MATCH_VERSION but still get legacy behavior
for vanity handler defaults should make hte burden of adding shards.qt=/select
to the "invariants" for each of their vanity handlers
> 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-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
