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

Shawn Heisey commented on SOLR-12303:
-------------------------------------

It might not seem like the right thing to you, but this is how Solr has been 
working for many years, and is expected behavior.  You can configure Solr to do 
what you want without a lot of trouble.

To specify which handler to use on shard requests, define the shards.qt 
parameter.  In your definition for /search, you can put this in the defaults 
section so that users do not need to specify it, or maybe in the invariants 
section so users can't override your choice.

It looks like the documentation is missing this parameter in the distributed 
search section.  I can find info about shards.qt in the reference guide if I 
already know what to search for, but it's not where I would expect it to be.

I will leave this issue open for now so that there can be a discussion about 
whether Solr should default the shards.qt parameter to the name of the handler. 
 If such a change is made, it is only going to happen in the next major version 
-- 8.0.  Changing a default like that in a minor version would cause many 
problems for existing users.


> Subquery doesn't inherit path from original request
> ---------------------------------------------------
>
>                 Key: SOLR-12303
>                 URL: https://issues.apache.org/jira/browse/SOLR-12303
>             Project: Solr
>          Issue Type: Bug
>      Security Level: Public(Default Security Level. Issues are Public) 
>            Reporter: Munendra S N
>            Priority: Major
>
> {code:java}
> localhost:8983/solr/k_test/search?sort=score desc,uniqueId 
> desc&q.op=AND&wt=json&q={!parent which=parent_field:true score=max}({!edismax 
> v=$origQuery})&facet=false&fl=uniqueId&fl=score&fl=_children_:[subquery]&fl=uniqueId&origQuery=false&qf=parent_field&_children_.fl=uniqueId&_children_.fl=score&_children_.rows=3&spellcheck=false&_children_.q={!edismax
>  qf=parentId v=$row.uniqueId}&rows=1
> {code}
> For this request, even though the path is */search*, the subquery request 
> would be fired on handler */select*.
> Subquery request should inherit the parent request handler and there should 
> be an option to override this behavior. (option to override is already 
> available by specifying *qt*)



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to