Skip to content

Add system_annotations_retention_days to ML APIs #522

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

Merged
merged 2 commits into from
Jul 30, 2021
Merged

Add system_annotations_retention_days to ML APIs #522

merged 2 commits into from
Jul 30, 2021

Conversation

lcawl
Copy link
Contributor

@lcawl lcawl commented Jul 29, 2021

@delvedor delvedor merged commit 18d4e03 into elastic:main Jul 30, 2021
@lcawl lcawl deleted the ml-system-annotations branch July 30, 2021 15:31
droberts195 added a commit to droberts195/elasticsearch-specification that referenced this pull request Aug 5, 2021
This is a reversion of elastic#522.

We decided not to add a new setting after all, but to
use results_retention_days for both results and system
annotations (on the basis that system annotations are
a type of result).

This setting has been added and removed within the 7.15
development cycle so there are no implications for
anyone using released product.
sethmlarson pushed a commit that referenced this pull request Aug 6, 2021
This is a reversion of #522.

We decided not to add a new setting after all, but to
use results_retention_days for both results and system
annotations (on the basis that system annotations are
a type of result).

This setting has been added and removed within the 7.15
development cycle so there are no implications for
anyone using released product.
sethmlarson pushed a commit that referenced this pull request Aug 6, 2021
This is a reversion of #522.

We decided not to add a new setting after all, but to
use results_retention_days for both results and system
annotations (on the basis that system annotations are
a type of result).

This setting has been added and removed within the 7.15
development cycle so there are no implications for
anyone using released product.
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