[
https://issues.apache.org/jira/browse/SOLR-7442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14516934#comment-14516934
]
Karl Wright commented on SOLR-7442:
-----------------------------------
bq. So I see no reason why a new httpclient such as Jetty's http client will
not work with old Solr installations.
The API for Jetty's HttpClient is completely different from the API for
HttpComponents/HttpClient. There are supported API entrypoints in SolrJ which
accept an HttpClient object, and for Solr Cloud there are methods you can
override which do the construction. Those obviously are not going to be
supported anymore if you ditch HttpComponents/HttpClient.
Please see
https://svn.apache.org/repos/asf/manifoldcf/trunk/connectors/solr/connector/src/main/java/org/apache/manifoldcf/agents/output/solr/HttpPoster.java
.
> HttpClient replacement for HTTP/2.0
> -----------------------------------
>
> Key: SOLR-7442
> URL: https://issues.apache.org/jira/browse/SOLR-7442
> Project: Solr
> Issue Type: New Feature
> Reporter: Ishan Chattopadhyaya
>
> Given that it would take about a year for Apache HC's HttpClient to support
> HTTP/2 (as per [~olegk] in SOLR-6865), adding this issue for exploring the
> way forward. It would be preferable to move to HTTP/2 and be able to use
> features like async http calls. Maybe we could look for alternatives to HC
> HttpClient, (e.g. Jetty's HttpClient)?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
