Bump ES output to include unicode-vs-compression fix #16012
Merged
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.
Release notes
Updates the Elasticsearch output to include a fix for situations where events containing non-unicode strings could be serialized incorrectly when sending to Elasticsearch with http compression enabled
What does this PR do?
Updates ES output to consume logstash-plugins/logstash-output-elasticsearch#1171
Why is it important/What is the impact to the user?
When compression is enabled and events contain non-unicode characters, without this fix invalid payloads could be sent to Elasticsearch resulting in indexing rejections.
Checklist
[ ] I have commented my code, particularly in hard-to-understand areas[ ] I have made corresponding changes to the documentation[ ] I have made corresponding change to the default configuration files (and/or docker env variables)[ ] I have added tests that prove my fix is effective or that my feature worksRelated issues
Use cases