Cherry-pick #16156 to 7.x: Include document_id in decode_json_fields allowed fields#16187
Merged
faec merged 1 commit intoelastic:7.xfrom Feb 7, 2020
Merged
Cherry-pick #16156 to 7.x: Include document_id in decode_json_fields allowed fields#16187faec merged 1 commit intoelastic:7.xfrom
faec merged 1 commit intoelastic:7.xfrom
Conversation
(cherry picked from commit 64713f9)
urso
approved these changes
Feb 7, 2020
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.
Cherry-pick of PR #16156 to 7.x branch. Original message:
What does this PR do?
This is a followup to #15859 which (among other things) added the
document_idfield to thedecode_json_fieldsprocessor, but forgot to also add it to the list of allowed fields in the processor registry, so libbeat rejected configurations that used it. This PR adds it to the allowed fields list.Checklist
I have made corresponding changes to the documentationI have made corresponding change to the default configuration files