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

Munendra S N commented on SOLR-12303:
-------------------------------------

 [^SOLR-12303.patch] 
1. Changed subqueryAugementer constructor where original request is an 
argument. With this client can't be passed to the constructor(I'm not sure if 
that's okay. One way is to add multiple constructors).
2. I have added tests to check the precedence of *qt* over parent path. There 
should also be a test to validate if parent path is inherited(I couldn't find a 
way to verify this, need help)

> Subquery Doc transform 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
>         Attachments: SOLR-12303.patch
>
>
> {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