[ML] frequent_items should not be a release highlight for 8.4 #89376
Conversation
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
The frequent_items aggregation is experimental in 8.4, and we want to gain confidence in it for internal use cases before publicising more widely, so we'll just give it a single bullet point release note rather than a whole section in the release highlights.
elasticsearchmachine
added
Team:Docs
|
Pinging @elastic/ml-core (Team:ML) |
|
Pinging @elastic/es-docs (Team:Docs) |
bearer-pipeline-test
pushed a commit
to BearerPipelineTest/elasticsearch
that referenced
this pull request
Aug 16, 2022
Copies a few changelog edits from the 8.4 branch into main so that people looking at the main branch see the same docs as people looking at 8.4. Relates elastic#89078 Relates elastic#89286 Relates elastic#89376
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
The frequent_items aggregation is experimental in 8.4, and we
want to gain confidence in it for internal use cases before
publicising more widely, so we'll just give it a single bullet
point release note rather than a whole section in the release
highlights.