[
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 auto-deprioritized-minor (was:
auto-deprioritized-major stale-minor)
Priority: Not a Priority (was: Minor)
This issue was labeled "stale-minor" 7 days ago and has not received any
updates so it is being deprioritized. If this ticket is actually Minor, please
raise the priority and ask a committer to assign you the issue or revive the
public discussion.
> 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: Not a Priority
> Labels: auto-deprioritized-major, auto-deprioritized-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)
