Shawn-Hx opened a new issue, #3419: URL: https://github.com/apache/fluss/issues/3419
### Search before asking - [x] I searched in the [issues](https://github.com/apache/fluss/issues) and found nothing similar. ### Motivation Currently, Fluss lake tiering can write data into Paimon, but the committed Paimon snapshots do not carry the tiering watermark. This makes it harder to understand the event-time progress of data synchronized from Fluss to the lake table. Paimon snapshot watermark can be used to better track the synchronization progress of lake tables. By reporting the watermark during tiering commits, users and downstream systems can inspect Paimon snapshots to know how far the lake table has caught up in event time. ### Solution Propagate watermark information through the lake tiering pipeline and report it when committing to Paimon. This includes extracting watermarks from Fluss records, carrying them for each split, aggregating them during tiering commit, and writing the final watermark into the committed Paimon snapshot. ### Anything else? _No response_ ### Willingness to contribute - [x] 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]
