Skip to content

commitlog: Include latest commit offset in segment metadata #2733

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

Merged
merged 1 commit into from
May 19, 2025

Conversation

kim
Copy link
Contributor

@kim kim commented May 14, 2025

Description of Changes

The segment metadata, obtained e.g. via committed_meta, will now include the start offset of the last commit read from the segment.

API and ABI breaking changes

No

Expected complexity level and risk

1

Testing

  • yes

@kim kim requested a review from Shubham8287 May 14, 2025 06:11
Copy link
Contributor

@Shubham8287 Shubham8287 left a comment

Choose a reason for hiding this comment

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

It looks correct, but I am missing intention behind this patch?
Is it to serve accepted_offset on fetch-api?

@kim
Copy link
Contributor Author

kim commented May 15, 2025

I needed to know the head commit's range from only the commitlog. Since the information is already there, it seemed convenient to expose it.

@kim
Copy link
Contributor Author

kim commented May 15, 2025

The motivation is more like determining an accepted offset for bootstrapping.

@kim kim added this pull request to the merge queue May 19, 2025
Merged via the queue into master with commit 1f4207d May 19, 2025
21 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants