Add shard_failures to EQL response spec#3372
Merged
Conversation
Contributor
|
Following you can find the validation results for the APIs you have changed.
You can validate these APIs yourself by using the |
pquentin
approved these changes
Dec 21, 2024
|
@luigidellaquila Does this need to be backported to 8.x as well? |
Contributor
Author
|
Uhm... yes, it needs a backport, thanks for pointing it out, I didn't realize I didn't do it. |
Contributor
Author
|
Added to my TODO list, I'll take care of it asap (unless there is some automation we can use on this repo) |
Contributor
Author
|
Created backport PR #3674 |
l-trotta
pushed a commit
that referenced
this pull request
Jan 31, 2025
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Adding shard_failures to the EQL response specification
Related to elastic/elasticsearch#116388
Follow-up to #3342