[
https://issues.apache.org/jira/browse/FLINK-29692?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17622950#comment-17622950
]
Benchao Li commented on FLINK-29692:
------------------------------------
Regarding "early-fire with window" versus "unbounded aggregate", I could share
a point. Usually they could do the same thing, but when come to the state
retiring, they will be a little different.
# window could retire state using watermark, and drop late event
# for unbounded aggregate, we could only set a state ttl, and there is no way
to drop late event
This is the most important reason why some use cases still prefer to use
"early-fire with window".
> 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.2
> 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)
