-
Notifications
You must be signed in to change notification settings - Fork 4.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add nested field yml support in elasticsearch template rendering #23183
Conversation
Pinging @elastic/security-external-integrations (Team:Security-External Integrations) |
💚 Build Succeeded
Expand to view the summary
Build stats
Test stats 🧪
Steps errorsExpand to view the steps failures
|
Test | Results |
---|---|
Failed | 0 |
Passed | 17502 |
Skipped | 1383 |
Total | 18885 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
…stic#23183) * Add nested field yml support in elasticsearch template rendering * Handle empty properties * Update changelog (cherry picked from commit ba7dbb6)
Since elastic#23183 was merged, `fields.yml` can now properly specify types for nested object properties
What does this PR do?
It looks like we don't handle subfields specified in
nested
fields properly. Here's the relevant Elasticsearch documentation:https://www.elastic.co/guide/en/elasticsearch/reference/current/nested.html
Currently it doesn't look like we use any non-dynamically mapped
nested
fields in ourfields.yml
specifications, so I'm fine doing this for the 7.12 release rather than 7.11.Checklist
CHANGELOG.next.asciidoc
orCHANGELOG-developer.next.asciidoc
.Related Issues
CC: @dcode