-
Notifications
You must be signed in to change notification settings - Fork 28.3k
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-50387][SS] Update condition for timer expiry and relevant test #48927
base: master
Are you sure you want to change the base?
Conversation
cc - @HeartSaVioR - PTAL, thx ! |
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 CI. Nice finding.
https://github.com/anishshri-db/spark/actions/runs/11964792826/job/33357779164 |
@HeartSaVioR - tried to run this locally and this fails even with/without my change. Let me merge back from master once |
@HeartSaVioR - verified on master and I see the same assert locally as well. So don't think its related to this change
@jingz-db @bogao007 - is this a known issue ? do we have a PR to fix this already ? |
I made a change previously to fix this issue https://github.com/apache/spark/pull/48805/files. Maybe 2s is not enough, @jingz-db could you help take a look? @anishshri-db There might be an issue running locally if it's using local time zone since the test is using UTC time, I need to use option |
What changes were proposed in this pull request?
Update condition for timer expiry and relevant test
Why are the changes needed?
To ensure that the expiry and removal conditions are consistent. Also, we don't have to wait for an extra microbatch to expire timers in certain cases.
Does this PR introduce any user-facing change?
Yes
How was this patch tested?
Added unit tests
Was this patch authored or co-authored using generative AI tooling?
No