Introduce elasticsearch nio library jar #27802
Assignees
Labels
:Distributed Coordination/Network
Http and internode communication implementations
>enhancement
v7.0.0-beta1
Comments
Tim-Brooks
added
:Distributed Coordination/Network
This was referenced Dec 14, 2017
Tim-Brooks
added a commit
that referenced
this issue
Dec 20, 2017
This is related to #27802. This commit adds a jar called elasticsearch-nio that contains the base nio classes that will be used for the tcp nio transport and eventually the http nio transport. The jar does not depend on elasticsearch:core, so all references to core have been removed.
|
Closed by 06b3130. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Currently our nio work lives in :test:framwork. This allows us to use nio as the basis for a test
TcpTransportimplementation in internal cluser integration tests. This verification is very valuable and we do not want to lose it. However, we need the base nio facilities to be available for creating a productionTcpTransportimplementation (in a plugin/module) and a production http transport implementation. This means that the base nio facilities need to be available elsewhere (while remaining available in :test:framwork).In order to do this, we need to introduce a nio library jar that provides the building blocks for creating transports based on nio. Ideally, this jar will not depend on elasticsearch:core as we would like to keep open the possibility that this nio work could eventually drive the rest client.
This is related to #27260.
The text was updated successfully, but these errors were encountered: