Cherry-pick #22521 to 7.x: Add basic wildcard/keyword fallback for upcoming ECS releases #22568
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 #22521 to 7.x branch. Original message:
What does this PR do?
This sets the groundwork for #21674 by adding a simple fallback mechanism for wildcard fields in unsupported Elasticsearch versions and non-OSS Beats distros. If you're publishing to ES < 7.9.0 you get
keyword
fields instead of wildcard, if you're coming from OSS Beats you get the same.This will allow us to move forward with the migration to ECS 1.7.0 with upcoming wildcard support..
Checklist
CHANGELOG.next.asciidoc
orCHANGELOG-developer.next.asciidoc
.