[ https://issues.apache.org/jira/browse/SOLR-16367?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
David Smiley updated SOLR-16367: -------------------------------- Description: This is an umbrella issue to migrate away from using Apache HttpClient to alternatives, namely Jetty HttpClient. Supporting both is hard to maintain, and furthermore Jetty supports HTTP 2. Sub-tasks and linked issues will accomplish this. When this umbrella is done, Apache HttpClient will not be used in solr-core or solrj. Modules may use it only if required by dependencies. HttpSolrClient (which uses Apache HttpClient) can still exist but in its own opt-in SolrJ module. (was: 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.) > Umbrella: Migrate away from Apache HttpClient. > ---------------------------------------------- > > 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 > > This is an umbrella issue to migrate away from using Apache HttpClient to > alternatives, namely Jetty HttpClient. Supporting both is hard to maintain, > and furthermore Jetty supports HTTP 2. Sub-tasks and linked issues will > accomplish this. When this umbrella is done, Apache HttpClient will not be > used in solr-core or solrj. Modules may use it only if required by > dependencies. HttpSolrClient (which uses Apache HttpClient) can still exist > but in its own opt-in SolrJ module. -- This message was sent by Atlassian Jira (v8.20.10#820010) --------------------------------------------------------------------- To unsubscribe, e-mail: issues-unsubscr...@solr.apache.org For additional commands, e-mail: issues-h...@solr.apache.org