Details
-
Improvement
-
Status: Open
-
Blocker
-
Resolution: Unresolved
-
None
-
None
-
None
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.
Attachments
Issue Links
- relates to
-
SOLR-15223 Deprecate Apache-HttpClient, refactor CloudSolrClient to use jetty-httpclient
- Closed
-
SOLR-17201 Make Http2SolrClients not experimental
- Closed
-
SOLR-16498 Tests need the URL from a SolrClient; don't require legacy clients
- Open
- requires
-
SOLR-16368 Refactoring: Use SolrClient type instead of overly specific subclasses
- Closed
1.
|
Convert CLI tools to Jetty HTTP 2 client. | Closed | Eric Pugh |
|
||||||||
2.
|
Switch UpdateShardHandler.getRecoveryOnlyHttpClient to Jetty HTTP2 | Resolved | David Smiley |
|
||||||||
3.
|
Switch UpdateShardHandler.getDefaultHttpClient to Jetty HTTP2 | Open | Unassigned |
|
||||||||
4.
|
Allow SolrClientCache clients to use Jetty HTTP2 clients | Closed | Alex Deparvu |
|
||||||||
5.
|
Update IndexFetcher Class to Use Http2SolrClient | Resolved | Unassigned | |||||||||
6.
|
Move RemoteSolrException to SolrClient in v10 | Resolved | Unassigned |
|
||||||||
7.
|
HttpSolrCall.remoteQuery should use Jetty HttpClient | Open | Unassigned | |||||||||
8.
|
Update SyncStrategy and PeerSyncWithLeader to use the recovery Http2SolrClient | Resolved | Sanjay Dutt |
|
||||||||
9.
|
Copy existing listeners on re-creation of Http2SolrClient | Resolved | Sanjay Dutt |
|