Skip to content
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

feat(storage): support next_epoch method for StateStoreReadLog #20068

Open
wants to merge 7 commits into
base: main
Choose a base branch
from

Conversation

wenym1
Copy link
Contributor

@wenym1 wenym1 commented Jan 8, 2025

I hereby agree to the terms of the RisingWave Labs, Inc. Contributor License Agreement.

What's changed and what's your intention?

Support next_epoch method for StateStoreReadLog. The method returns the next_epoch of the given epoch in the table change log.

Checklist

  • I have written necessary rustdoc comments.
  • I have added necessary unit tests and integration tests.
  • I have added test labels as necessary.
  • I have added fuzzing tests or opened an issue to track them.
  • My PR contains breaking changes.
  • My PR changes performance-critical code, so I will run (micro) benchmarks and present the results.
  • My PR contains critical fixes that are necessary to be merged into the latest release.

Documentation

  • My PR needs documentation updates.
Release note

@graphite-app graphite-app bot requested a review from a team January 8, 2025 02:48
@wenym1 wenym1 changed the base branch from main to yiming/no-state-store-write January 8, 2025 02:49
Copy link
Contributor Author

wenym1 commented Jan 8, 2025

Copy link
Collaborator

@hzxa21 hzxa21 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Rest LGTM!

@@ -148,12 +203,12 @@ impl<T> TableChangeLogCommon<T> {

pub fn truncate(&mut self, truncate_epoch: u64) {
while let Some(change_log) = self.0.front()
&& *change_log.epochs.last().expect("non-empty") <= truncate_epoch
&& *change_log.epochs.last().expect("non-empty") < truncate_epoch
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is this a bug fix?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not really. It just delays the truncation of the log on truncate_epoch, and is not wrong before this PR. After this PR, we need to keep the truncate_epoch in the change log.

@wenym1 wenym1 force-pushed the yiming/state-store-next-epoch branch from 7e04746 to f2ddc75 Compare January 9, 2025 08:38
@wenym1 wenym1 added this pull request to the merge queue Jan 10, 2025
@github-merge-queue github-merge-queue bot removed this pull request from the merge queue due to failed status checks Jan 10, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants