[
https://issues.apache.org/jira/browse/SOLR-17874?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18016696#comment-18016696
]
ASF subversion and git services commented on SOLR-17874:
--------------------------------------------------------
Commit 0ebe0a14ac939de5c1f980a5221a14dfa400d49d in solr's branch
refs/heads/main from David Smiley
[ https://gitbox.apache.org/repos/asf?p=solr.git;h=0ebe0a14ac9 ]
SOLR-17874: Stop using HttpSolrClient in production (#3501)
Switch remaining usages of Apache HttpClient to use the internally managed
Jetty HttpClient instance.
* shard split: the commits
* SYNCSHARD command/action
* admin handler (e.g. log level change with nodes param)
* IterativeMergeStrategy
* config edit API
* schema edit API
* NodesSysPropsCacher: use default client not that of shardHandler
Still using it in tests.
And removed some deprecated internal options to use Apache HttpClient
> core: Convert remaining HttpSolrClient to Http2SolrClient
> ---------------------------------------------------------
>
> Key: SOLR-17874
> URL: https://issues.apache.org/jira/browse/SOLR-17874
> Project: Solr
> Issue Type: Sub-task
> Reporter: David Smiley
> Priority: Major
> Labels: pull-request-available
> Time Spent: 40m
> Remaining Estimate: 0h
>
> Stop using HttpSolrClient or CloudLegacySolrClient or
> ConcurrentUpdateSolrClient in production code paths across Solr. Use Jetty
> based equivalents instead, typically obtained from an existing instance on
> CoreContainer. Most usages have already been removed but some remain.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
