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

David Smiley commented on SOLR-16367:
-------------------------------------

Perhaps migrating the tests are independent of migrating Solr-core.  Maybe 
[~bszabo97] you could just start.

Start a new PR... 
 # Find one usage in solr-core, migrate it.  Run tests.
 # If pass (or non-repeatable failures), commit and do more from the top.
 # If fail then commit and push; share an explanation of why it failed or at 
least the reproducible failure so any of us could trigger.  Stop; wait for 
feedback.

I anticipate there will be incompatibilities/problems relating to 
authentication, hopefully captured by tests.

 

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

Reply via email to