[jira] [Updated] (FLINK-21806) ContinuousEventTimeTrigger should register its first timer base on current watermark

["Flink Jira Bot (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/FLINK-21806?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Flink Jira Bot updated FLINK-21806:
-----------------------------------
    Labels: auto-deprioritized-major stale-minor  (was: auto-deprioritized-major)

I am the [Flink Jira Bot|https://github.com/apache/flink-jira-bot/] and I help the community manage its development. I see this issues has been marked as Minor but is unassigned and neither itself nor its Sub-Tasks have been updated for 180 days. I have gone ahead and marked it "stale-minor". If this ticket is still Minor, please either assign yourself or give an update. Afterwards, please remove the label or in 7 days the issue will be deprioritized.


> ContinuousEventTimeTrigger should register its first timer base on current watermark
> ------------------------------------------------------------------------------------
>
>                 Key: FLINK-21806
>                 URL: https://issues.apache.org/jira/browse/FLINK-21806
>             Project: Flink
>          Issue Type: Improvement
>          Components: API / DataStream
>    Affects Versions: 1.13.0
>            Reporter: Kezhu Wang
>            Priority: Minor
>              Labels: auto-deprioritized-major, stale-minor
>
> Currently, the first timer is registered base on timestamp of first element. But that that could be relative large in window. In case of {{maxTimestamp}}, then {{ContinuousEventTimeTrigger}} will never fire early.
> Due to compatibility, we might not able to change current behavior. How about an option in construction ?



--
This message was sent by Atlassian Jira
(v8.3.4#803005)