Extract transport #1347
Merged
Extract transport #1347
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
picandocodigo
force-pushed
the
extract_transport
branch
6 times, most recently
from
abad6c4 to
c9657e9
Compare
Initial commit on extracting Elasticsearch specific code from elasticsearch-transport and into the elasticsearch gem. We're now using transport for elastic-enterprise-search too.
picandocodigo
force-pushed
the
extract_transport
branch
3 times, most recently
from
f659fe2 to
ba9156f
Compare
picandocodigo
force-pushed
the
extract_transport
branch
from
ba9156f to
3d0862b
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Initial commit on extracting Elasticsearch specific code from
elasticsearch-transportand into theelasticsearchgem. We're now using transport for elastic-enterprise-search too.See #1344