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

David Smiley commented on SOLR-9215:
------------------------------------

For requestHandlers with a leading '/', you can only request them directly 
(without 'qt').  Otherwise, "qt" should work for request handlers that don't 
have a leading "/".  If I recall, handleSelect=true in solrconfig.xml might 
allow you to use "qt" even if it has a leading "/".  We ought to make this 
default to false for the next major release.

Confusing things a little is SolrJ... you can specify the request handler via 
the "qt" param (SolrQuery.setRequestHandler works this way).  When SolrJ issues 
the HTTP request, it will look at "qt" to see if it starts with a "/" and send 
it there.  I wish it would _also_ then remove 'qt' since it effectively 
consumed it's purpose but it does not, which is misleading when on the Solr 
side you see logged a qt param that Solr ignores server-side.

> QT parameter doesn't appear to function anymore
> -----------------------------------------------
>
>                 Key: SOLR-9215
>                 URL: https://issues.apache.org/jira/browse/SOLR-9215
>             Project: Solr
>          Issue Type: Bug
>    Affects Versions: 6.0, master (7.0)
>            Reporter: Markus Jelsma
>             Fix For: 6.1, master (7.0)
>
>
> The qt parameter doesn't seem to work anymore. A call directly to the /terms 
> handler returns actual terms, as expected. Using the select handler but with 
> qt=terms returns noting.
> http://localhost:8983/solr/logs/select?qt=terms&terms=true&terms.fl=compound_digest&terms.limit=100&terms.sort=index
> {code}
> <?xml version="1.0" encoding="UTF-8"?>
> <response>
> <lst name="responseHeader">
>   <int name="status">0</int>
>   <int name="QTime">0</int>
>   <lst name="params">
>     <str name="qt">terms</str>
>     <str name="indent">true</str>
>     <str name="terms.fl">compound_digest</str>
>     <str name="terms.limit">100</str>
>     <str name="terms.sort">index</str>
>   </lst>
> </lst>
> <result name="response" numFound="0" start="0">
> </result>
> </response>
> {code}
> A peculiar detail, my unit tests that rely on the qt parameter are not 
> affected.



--
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

Reply via email to