streams: fix stability/documentation #136642
Merged
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
pquentin
added
>non-issue
:Data Management/Data streams
elasticsearchmachine
added
the
Team:Data Management
Collaborator
|
Pinging @elastic/es-data-management (Team:Data Management) |
pquentin
added a commit
to pquentin/elasticsearch
that referenced
this pull request
Oct 18, 2025
This was referenced Oct 18, 2025
Collaborator
pquentin
added a commit
to pquentin/elasticsearch
that referenced
this pull request
Oct 18, 2025
elasticsearchmachine
pushed a commit
that referenced
this pull request
Oct 23, 2025
elasticsearchmachine
pushed a commit
that referenced
this pull request
Oct 23, 2025
chrisparrinello
pushed a commit
to chrisparrinello/elasticsearch
that referenced
this pull request
Oct 24, 2025
fzowl
pushed a commit
to voyage-ai/elasticsearch
that referenced
this pull request
Nov 3, 2025
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.
I'm reusing the values from elastic/elasticsearch-specification#5258, which seem more correct. (The context is that I'm working on generating rest-api-spec from the Elasticsearch specification, and I'm eliminating differences one by one first.)