Cherry-pick #24426 to 7.x: Add tests for encoding setting of filestream input#24629
Merged
kvch merged 1 commit intoelastic:7.xfrom Mar 18, 2021
Merged
Cherry-pick #24426 to 7.x: Add tests for encoding setting of filestream input#24629kvch merged 1 commit intoelastic:7.xfrom
kvch merged 1 commit intoelastic:7.xfrom
Conversation
(cherry picked from commit 1db96a3)
Contributor
|
Pinging @elastic/agent (Team:Agent) |
michalpristas
approved these changes
Mar 18, 2021
Contributor
💚 Build Succeeded
Expand to view the summary
Build stats
Test stats 🧪
Trends 🧪💚 Flaky test reportTests succeeded. Expand to view the summary
Test stats 🧪
|
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
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.
Cherry-pick of PR #24426 to 7.x branch. Original message:
What does this PR do?
Add support for configuring encoding and adds migrates related tests from
test_harvester.py.Why is it important?
Previously encoding could not be configured correctly from
configure. The underlying feature works it is already covered by numerous unit tests.Checklist
- [ ] I have made corresponding changes to the documentation- [ ] I have made corresponding change to the default configuration files- [ ] I have added an entry inCHANGELOG.next.asciidocorCHANGELOG-developer.next.asciidoc.