Include min transport version into FC response #136887
Open
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
idegtiarenko
added
>non-issue
:Search/Search
|
Pinging @elastic/es-search (Team:Search) |
nik9000
approved these changes
Oct 21, 2025
# Conflicts: # server/src/main/resources/transport/upper_bounds/9.3.csv
piergm
reviewed
Oct 22, 2025
server/src/main/java/org/elasticsearch/action/fieldcaps/FieldCapabilitiesResponse.java
Show resolved
Hide resolved
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 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.
This change includes min transport version into FC response (transport only).
This field can be beneficial for the consumer (such as ES|QL) that have behavior conditional on version of all indices data nodes.