Backport: Fix panic if user sets custom fields starting with host#10935
Merged
urso merged 2 commits intoelastic:6.7from Mar 3, 2019
Merged
Backport: Fix panic if user sets custom fields starting with host#10935urso merged 2 commits intoelastic:6.7from
urso merged 2 commits intoelastic:6.7from
Conversation
added 2 commits
February 25, 2019 16:25
The root cause has been fixed by elastic#10801 by accident already. This selectively backports the checks to 6.7, as elastic#10801 is to much of a change.
kvch
approved these changes
Feb 27, 2019
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
2 participants
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.
The root cause has been fixed by #10801 by accident already. This
selectively backports the checks to 6.7, as #10801 is to much of a
change.
Resolves: #10824