Hi Zihao, Thanks for the FLIP. I am worried that the proposal is mixing physical concerns (the downstream bursts of data) into logical semantics. I think a more natural escape hatch are hints. I also think that KEY_BASED is not really a physical optimization anyway, since it shifts window_start / window_end values in the output and therefore changes the result set. That makes it a poor fit for both a TVF argument and a hint, and probably a better fit for a PTF where the user explicitly owns the boundary assignment function.
Looking forward to your thoughts. Best regards, Martijn Op wo 20 mei 2026 om 14:32 schreef rocxing <[email protected]>: > > Hi Zihao and all, > > > Thanks a lot for this practical proposal. > This is a valuable feature for Flink SQL users, and we have also encountered > exactly the same pain points in our production environments. > Furthermore, the KEY_BASED deterministic stagger strategy is a good way to > eliminate non-determinism problems. > > > Best regards, > Pengxiang Wang
