Skip to content

Reorganize the update mechanisms for logStartOffset, LocalStartOffset, and remoteLogStartOffset #744

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.

Sign up for GitHub

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

Jump to bottom
Open
1 of 2 tasks
swuferhong opened this issue Apr 14, 2025 · 0 comments
Open
1 of 2 tasks

Reorganize the update mechanisms for logStartOffset, LocalStartOffset, and remoteLogStartOffset #744

swuferhong opened this issue Apr 14, 2025 · 0 comments
Labels
component=log

Comments

@swuferhong
Copy link
Collaborator

Search before asking

  • I searched in the issues and found nothing similar.

Fluss version

main (development)

Please describe the bug 🐞

Reorganize the update mechanisms for logStartOffset, LocalStartOffset, and remoteLogStartOffset. The most critical part is in rebuildWriterState, where LogTablet#logStartOffset() is used instead of the current value of 0.

Solution

No response

Are you willing to submit a PR?

  • I'm willing to submit a PR!
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
component=log
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@swuferhong