[
https://issues.apache.org/jira/browse/FLINK-6969?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16067618#comment-16067618
]
ASF GitHub Bot commented on FLINK-6969:
---------------------------------------
Github user wuchong commented on the issue:
https://github.com/apache/flink/pull/4183
Regarding to early firing, I think we are not on the same page and need to
discuss about what is early firing, how to configure it, how to implement it.
IMO, the early firing is to config an update rate of window. Such as an
one-hour window, but we want to see the result every minutes. So it is very
similar to
[FLINK-6649](https://issues.apache.org/jira/browse/FLINK-6649)(update rate for
non-windowed group), but this is a
update-rate/early-interval configuration on window group. If you agree with
that, then it is not a time offset of first result, because it can't describe
the rate.
Maybe we should move this discussion to the early firing issue FLINK-6961 ?
> Add support for deferred computation for group window aggregates
> ----------------------------------------------------------------
>
> Key: FLINK-6969
> URL: https://issues.apache.org/jira/browse/FLINK-6969
> Project: Flink
> Issue Type: New Feature
> Components: Table API & SQL
> Reporter: Fabian Hueske
> Assignee: sunjincheng
>
> Deferred computation is a strategy to deal with late arriving data and avoid
> updates of previous results. Instead of computing a result as soon as it is
> possible (i.e., when a corresponding watermark was received), deferred
> computation adds a configurable amount of slack time in which late data is
> accepted before the result is compute. For example, instead of computing a
> tumbling window of 1 hour at each full hour, we can add a deferred
> computation interval of 15 minute to compute the result quarter past each
> full hour.
> This approach adds latency but can reduce the number of update esp. in use
> cases where the user cannot influence the generation of watermarks. It is
> also useful if the data is emitted to a system that cannot update result
> (files or Kafka). The deferred computation interval should be configured via
> the {{QueryConfig}}.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
