CryoThrust commented on issue #11364:
URL: https://github.com/apache/seatunnel/issues/11364#issuecomment-5559822743

   The revised separation looks sound. One additional contract point before 
freezing the latest-snapshot model: distinguish report freshness from value 
quality. A fresh report may still be BEST_EFFORT/UNSUPPORTED, while an old 
EXACT value should be marked STALE rather than reused as current. For 
multi-attempt aggregation, I suggest retaining the winning (vertex, task, 
attempt, sequence) identity in the normalized snapshot and treating a lower 
attempt or sequence as an out-of-order update, not as a silent overwrite. This 
will make restart recovery and bounded metrics labeling deterministic without 
requiring checkpoint positions in v1.


-- 
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]

Reply via email to