[jira] [Comment Edited] (FLINK-29692) Support early/late fires for Windowing TVFs

["Aitozi (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/FLINK-29692?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17714815#comment-17714815 ] 

Aitozi edited comment on FLINK-29692 at 4/21/23 4:12 AM:
---------------------------------------------------------

hi, sorry for jumping into this discussion. I want to share two thoughts about this feature.
 * As [~jark] mentioned, in the group window aggregation the early/late fire has been supported. Window TVF as a feature-rich version of group window aggregation, so I think this ability should be aligned.
 * There is difference between the early/late fire and cumulate window tvf. early/late fire is something relates to the window trigger. But cumulative window relates to window assigner. We could use cumulative window to simulate the same functionality, but it may bring overhead as [~charles-tan] said.

So, +1 from my side to support emit strategy(early/late fire) in window TVF.


was (Author: aitozi):
hi, sorry for jumping into this discussion. I want to share two thoughts about this feature.
 * As [~jark] mentioned, in the group window aggregation the early/late fire has been supported. Window TVF as a feature-rich version of group window aggregation, so I think this ability should be aligned.
 * There is difference between the early/late fire and cumulate window tvf. early/late fire is something relates to the window trigger. But cumulative window relates to window assigner. We could use cumulative window to simulate the same functionality, but it may bring overhead as [~charles-tan] said.

So, +1 from my side to support emit strategy in window TVF.

> Support early/late fires for Windowing TVFs
> -------------------------------------------
>
>                 Key: FLINK-29692
>                 URL: https://issues.apache.org/jira/browse/FLINK-29692
>             Project: Flink
>          Issue Type: New Feature
>          Components: Table SQL / Planner
>    Affects Versions: 1.15.3
>            Reporter: Canope Nerda
>            Priority: Major
>
> I have cases where I need to 1) output data as soon as possible and 2) handle late arriving data to achieve eventual correctness. In the logic, I need to do window deduplication which is based on Windowing TVFs and according to source code, early/late fires are not supported yet in Windowing TVFs.
> Actually 1) contradicts with 2). Without early/late fires, we had to compromise, either live with fresh incorrect data or tolerate excess latency for correctness.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)