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

ASF subversion and git services commented on SOLR-18332:
--------------------------------------------------------

Commit 84b16f9d0af18e9fcc52ea9df2ba364ebb5f351f in solr's branch 
refs/heads/branch_10x from Eric Pugh
[ https://gitbox.apache.org/repos/asf?p=solr.git;h=84b16f9d0af ]

SOLR-18332: Small formatting fix to catch up with QT removal efforts in 
streaming (#4815)

(cherry picked from commit a7dbf28fac6c063a928fde22d1c5fe4f6df85ad2)


> Remove usages of deprecated 'qt' parameter and related SolrJ functionality
> --------------------------------------------------------------------------
>
>                 Key: SOLR-18332
>                 URL: https://issues.apache.org/jira/browse/SOLR-18332
>             Project: Solr
>          Issue Type: Improvement
>          Components: SolrJ
>    Affects Versions: main(11.0)
>            Reporter: Jason Gerlowski
>            Assignee: Jason Gerlowski
>            Priority: Minor
>              Labels: pull-request-available
>          Time Spent: 15h 10m
>  Remaining Estimate: 0h
>
> SOLR-17715 deprecated SolrQuery's setRequestHandler/getRequestHandler methods 
> in favor of a new QueryRequest ctor that takes an explicit requestHandler.  
> SolrJ users no longer need to send 'qt' to select a handler.
> There's some debate over whether this deprecation will "stick" and whether 
> we'll be able to eliminate all usages of qt, but in the meantime there are 
> many usages of 'qt' (and related methods) that are inarguably unnecessary. 
> This ticket tracks incrementally removing usages of the deprecated SolrJ 
> convenience methods / 'qt'-as-handler-override pattern in the codebase, in 
> cases where a path-based alternative exists.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

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

Reply via email to