Skip to content
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

[8.x] Add allow_partial_search_results and shard_failures to EQL (#3342) #3358

Merged
merged 2 commits into from
Dec 21, 2024

Conversation

luigidellaquila
Copy link
Contributor

(cherry picked from commit 5987f79)

@@ -3980,9 +3980,17 @@
"stability": "stable"
}
},
"description": "Create or update an index template.\nIndex templates define settings, mappings, and aliases that can be applied automatically to new indices.",
"description": "Create or update an index template.\nIndex templates define settings, mappings, and aliases that can be applied automatically to new indices.\nElasticsearch applies templates to new indices based on an index pattern that matches the index name.\n\nIMPORTANT: This documentation is about legacy index templates, which are deprecated and will be replaced by the composable templates introduced in Elasticsearch 7.8.\n\nComposable templates always take precedence over legacy templates.\nIf no composable template matches a new index, matching legacy templates are applied according to their order.\n\nIndex templates are only applied during index creation.\nChanges to index templates do not affect existing indices.\nSettings and mappings specified in create index API requests override any settings or mappings specified in an index template.",
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is completely unrelated, it was generated by make contrib (I ran it to resolve conflicts...).
Should it be reverted?

Copy link
Contributor

Following you can find the validation results for the API you have changed.

API Status Request Response
eql.search 🟢 32/32 32/32

You can validate this API yourself by using the make validate target.

@@ -1,5 +1,5 @@
{
"name": "elasticsearch-specification",
"name": "backport-8.x",
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Same here, maybe this just has to be reverted?

Copy link
Contributor

Following you can find the validation results for the APIs you have changed.

API Status Request Response
eql.delete 🟢 3/3 3/3
eql.get_status 🟢 3/3 3/3
eql.get 🟢 3/3 3/3
eql.search 🟢 37/37 37/37

You can validate these APIs yourself by using the make validate target.

@pquentin pquentin force-pushed the backport-3342-to-8.x branch from 3cdf4a5 to 4def748 Compare December 21, 2024 05:29
@pquentin pquentin changed the title Add spec for EQL allow_partial_search_results (#3342) [8.x] Add allow_partial_search_results and shard_failures to EQL (#3342) Dec 21, 2024
Copy link
Contributor

Following you can find the validation results for the APIs you have changed.

API Status Request Response
eql.delete 🟢 3/3 3/3
eql.get_status 🟢 3/3 3/3
eql.get 🟢 3/3 3/3
eql.search 🟢 37/37 37/37

You can validate these APIs yourself by using the make validate target.

@pquentin pquentin merged commit adf61fa into 8.x Dec 21, 2024
6 checks passed
@pquentin pquentin deleted the backport-3342-to-8.x branch December 21, 2024 05:33
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants