[
https://issues.apache.org/jira/browse/SOLR-12297?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Miller updated SOLR-12297:
-------------------------------
Description:
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.
was:
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.
> Create a good SolrClient for SolrCloud.
> ---------------------------------------
>
> 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
> 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.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
