ESQL: Use a 9.3-exclusive version for exp. histogram #139237
Merged
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.
#137432 added a minimum transport version to data types that are under construction, so that even in SNAPSHOT builds a coordinator node can decide whether other nodes or clusters are new enough to understand a data type that recently became supported in ESQL.
The
EXPONENTIAL_HISTOGRAMtype is one such type that is currently under construction. #137432 wrongly gave it a minimum transport version that was also backported to 9.2, even though the type is exclusive to 9.3 so far (even in SNAPSHOT builds).To keep things consistent, use a newer minimum transport version for
EXPONENTIAL_HISTOGRAM, namely the first version after it was added which was also not backported to 9.2.(There wasn't any breakage from this because we don't have tests that do anything with
EXPONENTIAL_HISTOGRAMin mixed 9.2/9.3 clusters/CCS to my knowledge.)