[
https://issues.apache.org/jira/browse/FLINK-29692?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17623154#comment-17623154
]
Jing Zhang commented on FLINK-29692:
------------------------------------
[~canopenerda] Thanks for sharing.
The demand is a
[deduplication|https://nightlies.apache.org/flink/flink-docs-master/docs/dev/table/sql/queries/deduplication]
on event time, get first row. But now time attribute is on millisecond unit
instead of microsecond. I guess it's also the reason why you choose early-fire
window.
How about use [topN|https://issues.apache.org/jira/browse/FLINK-23107]? top1
almost has well performance as good as
[deduplication|https://nightlies.apache.org/flink/flink-docs-master/docs/dev/table/sql/queries/deduplication]
because of [FLINK-23107|https://issues.apache.org/jira/browse/FLINK-23107].
> 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)
