-
Notifications
You must be signed in to change notification settings - Fork 3.7k
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
Add checking for new checkpoint #14353
Add checking for new checkpoint #14353
Conversation
@panhongan Have you tested this on a local druid cluster ? |
Yes, I tested in my local druid cluster. |
merge new code
@panhongan thank you for testing this on a cluster. Could you please look at the failing checks as well? |
merge latest code to branch
|
||
EasyMock.reset(spec); | ||
EasyMock.expect(spec.isSuspended()).andReturn(false).anyTimes(); | ||
EasyMock.expect(spec.getDataSchema()).andReturn(getDataSchema()).anyTimes(); |
Check notice
Code scanning / CodeQL
Deprecated method or constructor invocation
@AmatyaAvadhanula @cryptoe @pranavbhole |
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.
LGTM @panhongan!
Check that a checkpoint is non-empty before adding it to the checkpoint sequence in a SeekableStreamSupervisor
Fixes #XXXX.
org.apache.druid.indexing.seekablestream.supervisor.SeekableStreamSupervisor.CheckpointNotice#handle()
Description
There was NPE when parsed the
checkpoint
incontext
.I checked from the overlord log.
And the
checkpoint
containsnull
, like:Fixed the bug ...
Release note
Key changed classes in this PR
org.apache.druid.indexing.seekablestream.supervisor.SeekableStreamSupervisor.CheckpointNotice
This PR has: