luoyuxia opened a new issue, #2625: URL: https://github.com/apache/fluss/issues/2625
### Search before asking - [x] I searched in the [issues](https://github.com/apache/fluss/issues) and found nothing similar. ### Description see comment: https://github.com/apache/fluss/pull/2326#discussion_r2782986266 **Problem** When tiering commits both a readable snapshot and a committed (tiered) snapshot in the same run, the coordinator may record two lake snapshot metadata entries in one commit. The order of these entries is not guaranteed by snapshot timestamp. “latest” can then show the readable snapshot as latest which will be earlier than latest append snapshots. So, it breaks the semantics of latest snapshot. **Proposed solution** - Sort the lake snapshot metadatas list by snapshot timestamp (or equivalent total order). Treat only the most recent snapshot (last after sorting) as the effective committed snapshot for external visibility (e.g. “latest” snapshot). - Ensure all consumers of “latest snapshot” use this definition so visibility is consistent. ### Willingness to contribute - [ ] I'm willing to submit a PR! -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
