[
https://issues.apache.org/jira/browse/SOLR-6311?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14314656#comment-14314656
]
Noble Paul commented on SOLR-6311:
----------------------------------
[~hossman]
With InitParams , the behavior is exacly similar as if we have specified the
the config in the requestHandler itself
But, as you said, I expect users to configure a lot more paths with the
useParams feature with each mapping to a SearchHandler itself but a different
set of params and a nice descriptive name. Coupled with the fact that you can
change the params themselves pretty easily it will be more common. So you may
see paths like {{/bestproducts-by-rating}} {{/best-products-by-sale}} etc.
So it should not really hurt moving to shards.qt=qt
> 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: [email protected]
For additional commands, e-mail: [email protected]
