[
https://issues.apache.org/jira/browse/SOLR-7442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14516941#comment-14516941
]
Shalin Shekhar Mangar commented on SOLR-7442:
---------------------------------------------
Well, of course the Java API will be different. I was talking about protocol or
wire level compatibility between old SolrJ and new Solr server and vice-versa.
You could upgrade to the new SolrJ which may have an alternate client but it
will have a way of configuring whatever you were configuring earlier or you can
continue to use the old SolrJ which should be able to talk new Solr installs
for a while.
Again, all these are very early discussions. We're not even sure if http2 is
the right way or what client should we use or whether we want to use async IO
only between servers for a start and not between server and clients. It is also
possible, as you said earlier, that we may have a different Solrj
implementation for http2 than the current one and continue to support both for
a while.
> 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]
