Cherry-pick #17978 to 7.7: Changing field type to keyword #18093
Conversation
This file contains 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
* Changing field type to keyword * Adding changelog (cherry picked from commit 5cd6b52)
botelastic
bot
added
the
needs_team
ChrsMark
approved these changes
Apr 30, 2020
leweafan
pushed a commit
to leweafan/beats
that referenced
this pull request
Apr 28, 2023
…stic#18093) * Changing field type to keyword (elastic#17978) * Changing field type to keyword * Adding changelog (cherry picked from commit 179c1ce) * update changelog Co-authored-by: Stijn Holzhauer <[email protected]>
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 #17978 to 7.7 branch. Original message:
What does this PR do?
Modify the field type from filebeat/nginx module fields from text to keyword as requested in #17834
Why is it important?
See Issue #17834
Checklist
I have commented my code, particularly in hard-to-understand areasI have made corresponding change to the default configuration filesI have added tests that prove my fix is effective or that my feature worksCHANGELOG.next.asciidocorCHANGELOG-developer.next.asciidoc.Related issues
Note
First PR ever, go easy on me ;)