-
Notifications
You must be signed in to change notification settings - Fork 25.6k
Using the STREAMS_LOGS_SUPPORT_8_19 transport version #129796
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
lukewhiting
merged 5 commits into
elastic:main
from
masseyke:use-streams_logs_support_8_19
Jun 23, 2025
Merged
Changes from 3 commits
Commits
Show all changes
5 commits
Select commit
Hold shift + click to select a range
e56dfd6
Using the STREAMS_LOGS_SUPPORT_8_19 transport version
masseyke daef732
Update StreamsMetadata.java
masseyke a115bd0
Merge branch 'main' into use-streams_logs_support_8_19
lukewhiting 20d10fe
Return minimal supported version as 8.19 for metadata object to fix t…
lukewhiting 87c3d74
Merge branch 'main' into use-streams_logs_support_8_19
lukewhiting File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Are you sure that it's safe to return null here? It has a few callers outside of the default implementation of
supportsVersion(), including inAbstractNamedDiffable.diff()(directly or indirectly, on both code paths).I see a couple of different patterns elsewhere in the codebase where
supportVersion()is overridden.MinimalServiceSettings.supportsVersionandModelRegistryMetadatahave the same logic to what you have here, andgetMinimalSupportedVersion()returns the_8_19version.AggregateMetricDoubleBlockBuilder,NoneChunkingSetting, andPinnedRankDocmake this method, e.g. the first of those doesthrow new UnsupportedOperationException("must not be called when overriding supportsVersion").(There's also
TimeSeriesSourceOperator.Statuswhere the two methods don't seem to agree on the minimal version, I haven't looked properly at that.)If we're sure this method will never be called, I would prefer to throw an exception with an explicit message like e.g.
AggregateMetricDoubleBlockBuilderdoes, so that if we're wrong we'll get something more helpful than an NPE somewhere later on. I don't know whether that or returning the_8_19version is safer.Hopefully someone from Core/Infra can sort us out here?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We tried throwing an exception originally but it causes the tests to fail too. It seems returning
TransportVersions.STREAMS_LOGS_SUPPORT_8_19fixes the test fails so that looks to be like it's the right path possibly?Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Since there is a precedent for doing it, it fixes the tests, let's maybe go with this and see what Core/Infra have to say.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
FWIW, I'm throwing an exception in this somewhat related PR, and that works fine.