[
https://issues.apache.org/jira/browse/FLINK-29692?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17621167#comment-17621167
]
Jark Wu commented on FLINK-29692:
---------------------------------
I'm fine with supporting this feature. But we have supported early/late fires
for the legacy group window aggregation. You can use {{last_value(col)}} agg
function to get window deduplication result. For example:
{code:sql}
-- output window result for every 5 seconds before window fire
SET table.exec.emit.early-fire.enabled = true;
SET table.exec.emit.early-fire.delay = 5s;
-- emit window result for every late arriving record
SET table.exec.emit.late-fire.enabled = true;
SET table.exec.emit.late-fire.delay = 0;
SELECT TUMBLE_START(rowtime, INTERVAL '5' MINUTES), last_value(col_a),
last_value(col_b)
FROM my_source_table
GROUP BY mykey, TUMBLE(rowtime, INTERVAL '5' MINUTES);
{code}
> 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)
