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

Hoss Man commented on SOLR-6311:
--------------------------------

bq.  It should have been done this way to begin with. I consider it a bug that 
distributed requests were apparently hard-coded to use /select

Definitely not a bug.

you have to remember the context of how distributed search was added -- prior 
to SolrCloud, you had to specify a "shards" param listing all of the cores you 
wanted to do a distributed search over, and the primary convinience mechanism 
for doing that was to register a handler like this...

{noformat}
<requestHandler name="/my_handler" class="solr.SearchHandler"/>
  <lst name="defaults">
    <str name="shards">foo:8983/solr,bar:8983/solr</str>
    <int name="rows">100</int>
  </lst>
</requestHandler>
{noformat}

...so the choice to have "shards.qt" default to "/select" instead of the 
current qt was _extremely_ important to make distributed search function 
correctly for most users for multiple reasons:

1) so that the shards param wouldn't cause infinite recursion
2) so that the "defaults" wouldn't be automatically inherited by the per-shard 
requests

But now is not then -- the default behavior of shards.qt should change to make 
the most sense given the features and best practice currently available in 
Solr.  SolrCloud solves #1, and IIUC useParams solves #2, so we can move 
forward.


> 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
>            Assignee: Timothy Potter
>         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]

Reply via email to