[Failure store] Add data stream options to the es specs#4414
Conversation
output/schema/validation-errors.json
Outdated
| "indices.get_data_stream_options": { | ||
| "request": [ | ||
| "Request: missing json spec query parameter 'include_defaults'" | ||
| ], | ||
| "response": [] | ||
| }, |
There was a problem hiding this comment.
About this param. Currently, this flag has no effect. It is already in the API because initially, we considered to expose the default rollover via this flag, but we did not do this. @jbaiera can we clean it up from the API, or should I add it here and explain that it doesn't have an effect yet?
There was a problem hiding this comment.
If the flag has no effect and we aren't planning on adding anything for it, we should probably just remove it from the API. Considering the api is so recently new and it hasn't been fully documented yet, I think it's a pretty low impact change to pursue.
There was a problem hiding this comment.
I was hoping you would day that, I opened elastic/elasticsearch#128730
| @@ -1,5 +1,5 @@ | |||
| # summary: | |||
| description: A successful response from `GET _lifecycle/stats?human&pretty`. | |||
| description: A successful response from `GET /_data_stream/{name}/_lifecycle?human&pretty`. | |||
There was a problem hiding this comment.
Drive-by fix, this is not the lifecycle stats API.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
| "include_defaults": { | ||
| "type": "boolean", | ||
| "description": "Return all relevant default configurations for the data stream (default: false)" | ||
| }, |
|
Following you can find the validation results for the APIs you have changed.
You can validate these APIs yourself by using the |
|
The backport to To backport manually, run these commands in your terminal: # Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add .worktrees/backport-8.19 8.19
# Navigate to the new working tree
cd .worktrees/backport-8.19
# Create a new branch
git switch --create backport-4414-to-8.19
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 00be10ac5ace4211ff41c0c640eb9b6ecaf10f07
# Push it to GitHub
git push --set-upstream origin backport-4414-to-8.19
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-8.19Then, create a pull request where the |
(cherry picked from commit 00be10a) # Conflicts: # output/openapi/elasticsearch-openapi.json # output/openapi/elasticsearch-serverless-openapi.json # output/schema/schema.json # output/typescript/types.ts # specification/indices/_types/IndexTemplate.ts
💚 All backports created successfully
Questions ?Please refer to the Backport tool documentation |
|
I had completely missed this.... |
(cherry picked from commit 00be10a) # Conflicts: # output/openapi/elasticsearch-openapi.json # output/openapi/elasticsearch-serverless-openapi.json # output/schema/schema.json # output/typescript/types.ts # specification/indices/_types/IndexTemplate.ts Co-authored-by: Mary Gouseti <mary.gouseti@elastic.co>
As part of the failure store feature, we introduce the data stream options. Data stream options have the following format:
Currently they only configure the failure store and they can be set in their dedicated APIs and via the templates.