You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@fluss.apache.org by "gyang94 (via GitHub)" <gi...@apache.org> on 2026/08/11 07:39:01 UTC
[PR] [server] Clarify remote log start offset semantics [fluss]
gyang94 opened a new pull request, #3942:
URL: https://github.com/apache/fluss/pull/3942
### Purpose
This is a follow-up to #3937.
Keep the remote log start offset reported by the manifest and tablet aligned with the manifest-visible logical range. A replacement object may physically start before the current visible range; for example, a physical object covering `[5, 25)` can be visible only from offset `10`. Reporting physical offset `5` would incorrectly expose an expired prefix.
### Brief change log
- return the logical start offset from `RemoteLogManifest`
- rename physical segment start-offset APIs to `physicalStartOffset`
- rename propagated start-offset fields and variables so logical and physical semantics are explicit
- leave all remote log end-offset APIs and semantics unchanged
- add regression coverage for a physical start offset preceding the manifest-visible logical start
### Tests
- `mvn -o -pl fluss-common -DskipITs -Dfast -Dtest=RemoteLogManifestOverlapTest test`
- `mvn -o -pl fluss-server -am -DskipITs -Dfast -Dtest=RemoteLogTabletOverlapTest,RemoteLogTabletTest,RemoteLogManagerTest -Dsurefire.failIfNoSpecifiedTests=false test`
- `mvn -o -pl fluss-client,fluss-server,fluss-flink/fluss-flink-common -am -DskipTests -Dfast package`
### API and Format
This renames internal Java APIs for remote segment physical start offsets. It does not change the RPC wire format, manifest storage format, or remote log end-offset semantics.
### Documentation
No user-facing documentation changes are required.
### Generative AI disclosure
- [x] Yes — Codex (GPT-5)
<!-- Generated-by: Codex (GPT-5) following https://github.com/apache/fluss/blob/main/AGENTS.md -->
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscribe@fluss.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [PR] [server] Clarify remote log start offset semantics [fluss]
Posted by "wuchong (via GitHub)" <gi...@apache.org>.
wuchong closed pull request #3942: [server] Clarify remote log start offset semantics
URL: https://github.com/apache/fluss/pull/3942
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscribe@fluss.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [PR] [server] Clarify remote log start offset semantics [fluss]
Posted by "wuchong (via GitHub)" <gi...@apache.org>.
wuchong commented on PR #3942:
URL: https://github.com/apache/fluss/pull/3942#issuecomment-5264751727
Continue with https://github.com/apache/fluss/pull/3956
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscribe@fluss.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org