-
Notifications
You must be signed in to change notification settings - Fork 28.5k
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
[SPARK-50360][SS][FOLLOWUP][MINOR] Make readVersion lazy value #49091
Conversation
...core/src/main/scala/org/apache/spark/sql/execution/streaming/state/StateStoreChangelog.scala
Outdated
Show resolved
Hide resolved
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.
+1 pending tests, thanks for the follow up!
@HeartSaVioR |
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.
Could you please add SPARK ticket label to the title as it's a follow-up from existing JIRA ticket?
...core/src/main/scala/org/apache/spark/sql/execution/streaming/state/StateStoreChangelog.scala
Outdated
Show resolved
Hide resolved
I think it should be renamed as
|
@HeartSaVioR |
The failure only happened with TPC, which isn't relevant. |
Thanks! Merging to master. |
Forgot to call out +1 |
What changes were proposed in this pull request?
This is followup to #48880
readVersion
is made alazy
value.After
input
is closed, its value is not changed tonull
becauseinput
is only used byreadVersion
.Why are the changes needed?
StateStoreChangelogReaderFactory
is able to produce more than one reader.Does this PR introduce any user-facing change?
No
How was this patch tested?
Existing test suite.
Was this patch authored or co-authored using generative AI tooling?
No