[
https://issues.apache.org/jira/browse/SOLR-16367?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17624455#comment-17624455
]
David Smiley commented on SOLR-16367:
-------------------------------------
That's it in a nutshell. But there are a number of cases where we can't simply
switch over, and so there is preparatory work. See
https://issues.apache.org/jira/browse/SOLR-16368?focusedCommentId=17624453&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-17624453
where many tests assume a legacy client merely to get the URL/Apache
HttpClient.
> Switch from CloudLegacySolrClient to CloudSolrClient
> ----------------------------------------------------
>
> Key: SOLR-16367
> URL: https://issues.apache.org/jira/browse/SOLR-16367
> Project: Solr
> Issue Type: Improvement
> Security Level: Public(Default Security Level. Issues are Public)
> Reporter: David Smiley
> Priority: Major
>
> CloudLegacySolrClient is deprecated; it uses the Apache HTTP client.
> CloudSolrClient uses the Jetty HTTP client, which supports HTTP 2. In this
> issue, switch all of Solr to not use CloudLegacySolrClient anymore.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
