Cherry-pick #23673 to 7.x: Swap ECS 1.7 experimental schema with non-experimental to revert wildcard changes #23700
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
…card changes (elastic#23673) * Swap ECS 1.7 experimental schema with non-experimental to revert wildcard changes * Add back in user.effective.* fields to auditd integrations due to no longer using experimental schema (cherry picked from commit 0f50eb7)
|
Pinging @elastic/security-external-integrations (Team:Security-External Integrations) |
botelastic
bot
added
needs_team
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 #23673 to 7.x branch. Original message:
What does this PR do?
This PR changes the experimental ECS 1.7 schema that we were going to use in 7.11 to be the ECS 1.7 non-experimental version. This coincides with the Elasticsearch performance regressions that we saw on some widely used filebeat modules as mentioned in #23671. The fallback logic introduced to support wildcard fields can stay since the schema itself is switching back from
wildcardtokeyword. The intent is to proceed at a more judicious pace with wildcard adoption in coming releases.Checklist
- [ ] I have added an entry inCHANGELOG.next.asciidocorCHANGELOG-developer.next.asciidoc.Related issues