[
https://issues.apache.org/jira/browse/FLINK-29692?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17715100#comment-17715100
]
Chalres Tan commented on FLINK-29692:
-------------------------------------
re [~jark]: Thanks for the response. The example query you provided would yield
the correct results, but from my understanding with window TVF, after the
window expires then the state associated with that window will be cleared. With
the example you provided, is it true that the state will just accumulate over
time? Also, the approach with the query won't work by adjusting the use case
slightly. For example, if instead of 1 hour tumbling windows they were 2 hour
windows or if instead of using tumbling windows we had hopping windows with
length 1 hour every 30 minutes.
> 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)
