[
https://issues.apache.org/jira/browse/SOLR-17715?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18080802#comment-18080802
]
ASF subversion and git services commented on SOLR-17715:
--------------------------------------------------------
Commit ec9702918af237c34f683f563ec1c7488a29d6ce in solr's branch
refs/heads/branch_9_11 from r4mercur
[ https://gitbox.apache.org/repos/asf?p=solr.git;h=ec9702918af ]
SOLR-17715: Stop sending qt param from SolrJ (#4397)
Enhanced QueryRequest with explicit support for the path, avoiding the need for
"qt".
(cherry picked from commit 4d2720a0e906ff4a6e836e54802b7f283664366b)
(cherry picked from commit d458d94b065a7245da82c0995cb77fb12002fd7c)
> SolrJ / QueryRequest - stop sending "qt" param
> ----------------------------------------------
>
> Key: SOLR-17715
> URL: https://issues.apache.org/jira/browse/SOLR-17715
> Project: Solr
> Issue Type: Task
> Components: SolrJ
> Reporter: David Smiley
> Priority: Major
> Labels: newdev, pull-request-available
> Time Spent: 3h 20m
> 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.
> ----
> Originally this issue was basically "deprecate qt" but now it's morphed to be
> a QueryRequest improvement with additional constructors so callers can be
> explicit about the path without resorting to "qt", and also includes some
> "qt" filtering here.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
