Skip to content

[server] Fix remote log start offset of RemoteLogManifest may expose an expired physical prefix - #3956

Merged
wuchong merged 4 commits into
apache:mainfrom
gyang94:codex/fix-remote-log-logical-offset-minimal
Aug 12, 2026
Merged

wuchong merged 4 commits into
apache:mainfrom
gyang94:codex/fix-remote-log-logical-offset-minimal

Conversation

@gyang94

@gyang94 gyang94 commented Aug 12, 2026

Copy link
Copy Markdown
Contributor

Purpose

Remote log manifests can expose a logical range narrower than the physical ranges of their persisted segments. The aggregate manifest offsets are propagated as the remotely readable range, so they must be derived from logical boundaries.

Brief change log

  • Make RemoteLogManifest#getRemoteLogStartOffset return the minimum logical start offset.
  • Make RemoteLogManifest#getRemoteLogEndOffset return the maximum logical end offset.
  • Preserve the existing Java API and RPC field names.
  • Add coverage for manifests with clipped physical prefixes and suffixes.

Tests

  • mvn -o -pl fluss-common -Dtest=RemoteLogManifestOverlapTest test
  • Checkstyle and Spotless passed as part of the Maven lifecycle.

API and Format

No API, RPC field, or storage-format changes.

Documentation

No documentation changes.

Generative AI disclosure

  • Yes — Codex (gpt-5)

Report the manifest-visible logical range through the existing remote log offset accessors without renaming the API or RPC fields.

Co-Authored-By: Codex <noreply@openai.com>

AI-Model: gpt-5

AI-Contributed/Feature: 8/8

AI-Contributed/UT: 11/11
@gyang94
gyang94 marked this pull request as ready for review August 12, 2026 06:56
Clarify that the existing remote log offset accessors expose the manifest logical range, which may differ from physical segment boundaries.

Co-Authored-By: Codex <noreply@openai.com>

AI-Model: gpt-5

AI-Contributed/Feature: 18/18

AI-Contributed/UT: 0/0
Put the manifest-visible logical range semantics first and remove the unnecessary comparison with the last segment physical end offset.

Co-Authored-By: Codex <noreply@openai.com>

AI-Model: gpt-5

AI-Contributed/Feature: 20/20

AI-Contributed/UT: 0/0
Keep the documentation focused on the manifest-visible logical range.

Co-Authored-By: Codex <noreply@openai.com>

AI-Model: gpt-5

AI-Contributed/Feature: 6/6

AI-Contributed/UT: 0/0

@wuchong wuchong left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

LGTM.

@wuchong wuchong linked an issue Aug 12, 2026 that may be closed by this pull request
2 tasks done
@wuchong wuchong changed the title [server] Use logical remote log offsets [server] Fix remote log start offset of RemoteLogManifest may expose an expired physical prefix Aug 12, 2026
@wuchong
wuchong merged commit 7f7fe24 into apache:main Aug 12, 2026
19 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.

Remote log start offset may expose an expired physical prefix

2 participants