You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@flink.apache.org by "Kurt Young (JIRA)" <ji...@apache.org> on 2019/01/30 09:47:00 UTC

[jira] [Closed] (FLINK-6961) Enable configurable early-firing rate

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

Kurt Young closed FLINK-6961.
-----------------------------
    Resolution: Unresolved

> Enable configurable early-firing rate 
> --------------------------------------
>
>                 Key: FLINK-6961
>                 URL: https://issues.apache.org/jira/browse/FLINK-6961
>             Project: Flink
>          Issue Type: New Feature
>          Components: Table API &amp; SQL
>            Reporter: Shaoxuan Wang
>            Priority: Major
>
> There are cases that we need to emit the result earlier to allow user get an observation/sample of the result. Right now, only the unbounded aggregate works in early-firing mode (in the future we will support early firing for all different scenarios, like windowed aggregate, unbounded/windowed join, etc.). But in unbounded aggregate, the result is prepared and emitted for each input. This may not be necessary, as user may not need to get the result so frequent in most cases.
> We create this Jira to track all the efforts (sub-jira) to enable configurable early-firing rate. It should be noted that the early-firing rate will not be exposed to the user, it will be smartly decided by the query optimizer depending on the SLA(allowed latency) of the final result.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)