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.
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
[Security Solution] Migrates siem-detection-engine-rule-status alertId to saved object references array #114585
[Security Solution] Migrates siem-detection-engine-rule-status alertId to saved object references array #114585
Changes from all commits
bec9779
bbb7fc3
bd30df7
0ec7dd6
122f015
a55c1d0
2bf2bd9
503e55b
e31c9da
5f41332
ddccdfe
8cd206e
248b197
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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.
Ended up running into issues going the two query route as well too as it wasn't possible to do a
nested
top_hits
agg and sort on a parent field without specifyingreverse_nested
.... 😅Touched base w/ @XavierM and just ended up adding support for
reverse_nested
here. So now we're still able to complete this operation in a single query, and can keep the same extractions logic below as before. 🙂