[
https://issues.apache.org/jira/browse/SOLR-17715?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18017759#comment-18017759
]
ASF subversion and git services commented on SOLR-17715:
--------------------------------------------------------
Commit 86e4757921ad66990d957ee8d8418983fa73ead6 in solr's branch
refs/heads/branch_9x from David Smiley
[ https://gitbox.apache.org/repos/asf?p=solr.git;h=86e4757921a ]
SOLR-17715: Deprecate SolrQuery.setRequestHandler (#3600)
and getRequestHandler.
Use setPath instead.
(cherry picked from commit bdfb1219a81e63e4146a0994972d6670ebbd20dd)
> Remove "qt" param path support in SolrJ
> ---------------------------------------
>
> Key: SOLR-17715
> URL: https://issues.apache.org/jira/browse/SOLR-17715
> Project: Solr
> Issue Type: Task
> Components: SolrJ
> Reporter: David Smiley
> Priority: Blocker
> Labels: newdev, pull-request-available
> Fix For: main (10.0)
>
> Time Spent: 2h 10m
> Remaining Estimate: 0h
>
> SolrJ doesn't need the "qt" param; SolrJ can create requests with whatever
> the desired path should be as a parameter to the SolrRequest constructor.
> The "qt" param complicates interpreting a request to know where to send it.
> And it still shows up on the request, which the Solr backend hasn't handled
> for a long time.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
