zuston opened a new pull request, #3350: URL: https://github.com/apache/fluss/pull/3350
### Purpose Linked issue: close #3349 Flink currently exposes `currentFetchEventTimeLag`, but it measures event-time lag rather than offset backlog. For Fluss log reading, we need a Kafka-style records lag metric so users can understand how far each subscribed source-reader bucket is behind. Relying only on timestamp lag can be misleading, especially for backfill jobs that subscribe to multiple time partitions. Older partitions may always appear to have a large event-time lag, even when their records have already been fully consumed. ### Brief change log <!-- Please describe the changes made in this pull request and explain how they address the issue --> ### Tests <!-- List UT and IT cases to verify this change --> ### API and Format <!-- Does this change affect API or storage format --> ### Documentation <!-- Does this change introduce a new feature --> -- 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]
