-
Notifications
You must be signed in to change notification settings - Fork 588
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
Remove RaftLogReader#isEmpty #6339
Conversation
Ah, wait, this PR is based on a different branch. Let me rebase before you review. |
b92f1fd
to
6aa7e74
Compare
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.
This doesn't remove isEmpty
from the JournalReader and all its implementations. Is there a reason you're keeping those?
Right now to keep the PR small and focused, as it seemed a bit out of scope for me - I would like to challenge the use of |
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.
bors r+
Build succeeded: |
* fix: improve error messages for select filters * fix: reuse already created error message object to avoid code duplication, remove unused date property
Description
This PR removes
RaftLogReader#isEmpty
in order to simplify #6307. It removes the call to check if the journal is empty and simply scans the log forZeebeEntry
. This is a naive implementation which may be slow, however in practice the log is made up of mostlyZeebeEntry
, or it's empty - in which case it should return fairly quickly.Related issues
related to #6307
Definition of Done
Not all items need to be done depending on the issue and the pull request.
Code changes:
backport stable/0.25
) to the PR, in case that fails you need to create backports manually.Testing:
Documentation: