[
https://issues.apache.org/jira/browse/FLINK-29692?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17623595#comment-17623595
]
Jakub Partyka commented on FLINK-29692:
---------------------------------------
{quote}Could you describe the demand in detail [~canopenerda] [~jjpar] , thanks
a lot.
Let's see if there are other better plans which could satisfy your demands,
such as [cumulate window
tvf?|https://nightlies.apache.org/flink/flink-docs-release-1.14/zh/docs/dev/table/sql/queries/window-tvf/#cumulate]
{quote}
In my case I have a source, that has event time and watermark time in different
columns. Watermark column guarantees, that all events with event time <=
watermark time had arrived. But this watermark has greater delay, and we are
working with minute-sized windows. Therefore we use early fire to emit
intermediate results, without waiting for watermark.
> 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)
