Elasticsearch5 sink #117
Closed
Elasticsearch5 sink #117
Conversation
This file contains hidden or 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
waidr
pushed a commit
to waidr/flume
that referenced
this pull request
Jul 24, 2019
uplog custom format
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Hi Flume team,
I worked for my company on this patch to be able to use ElasticSearch 5 with flume.
We heavy use Flume with Hadoop and ElasticSearch as well.
We are testing this patch that seams to work properly
I thought it could be helpfull for some of your users
Let me know if you have any questions
Geoffroy