You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Shawn Heisey (JIRA)" <ji...@apache.org> on 2018/06/02 00:29:00 UTC
[jira] [Commented] (SOLR-12297) Create a good SolrClient for
SolrCloud paving the way for async requests, HTTP2, multiplexing, and the
latest & greatest Jetty features.
[ https://issues.apache.org/jira/browse/SOLR-12297?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16498754#comment-16498754 ]
Shawn Heisey commented on SOLR-12297:
-------------------------------------
[~markrmiller@gmail.com] if I am confusing things or making life harder for you, I do apologize. I'm trying to be helpful.
On the Jetty side, things have moved from the issue I linked above to another:
https://github.com/eclipse/jetty.project/issues/1350
There isn't currently a client that can use both protocols. The idea of using two HttpClient objects within the solr client is something I was thinking I might explore.
FYI, I'm in this particular rabbit hole because I'm trying to get the server started on starburst. I worked through some classloader issues (I have a patch for you that only touches the ivy config) and finally did manage to get the server started. But as soon as I tried "bin/solr create" to create a core, it didn't work. I also tried forcing http 1.1 in SolrCLI and that didn't help, but I haven't had a chance to discover whether I did something wrong.
> Create a good SolrClient for SolrCloud paving the way for async requests, HTTP2, multiplexing, and the latest & greatest Jetty features.
> ----------------------------------------------------------------------------------------------------------------------------------------
>
> Key: SOLR-12297
> URL: https://issues.apache.org/jira/browse/SOLR-12297
> Project: Solr
> Issue Type: New Feature
> Security Level: Public(Default Security Level. Issues are Public)
> Reporter: Mark Miller
> Assignee: Mark Miller
> Priority: Major
>
> Blocking or async support as well as HTTP2 compatible with multiplexing.
> Once it supports enough and is stable, replace internal usage, allowing async, and eventually move to HTTP2 connector and allow multiplexing. Could support HTTP1.1 and HTTP2 on different ports depending on state of the world then.
> The goal of the client itself is to work against HTTP1.1 or HTTP2 with minimal or no code path differences and the same for async requests (should initially work for both 1.1 and 2 and share majority of code).
> The client should also be able to replace HttpSolrClient and plug into the other clients the same way.
> I doubt it would make sense to keep ConcurrentUpdateSolrClient eventually though.
> I evaluated some clients and while there are a few options, I went with Jetty's HttpClient. It's more mature than Apache HttpClient's support (in 5 beta) and we would have to update to a new API for Apache HttpClient anyway.
> Meanwhile, the Jetty guys have been very supportive of helping Solr with any issues and I like having the client and server from the same project.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org