[ 
https://issues.apache.org/jira/browse/FLINK-12794?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17323250#comment-17323250
 ] 

Flink Jira Bot commented on FLINK-12794:
----------------------------------------

This issue is assigned but has not received an update in 7 days so it has been 
labeled "stale-assigned". If you are still working on the issue, please give an 
update and remove the label. If you are no longer working on the issue, please 
unassign so someone else may work on it. In 7 days the issue will be 
automatically unassigned.

> Support ACC mode for non-window streaming FlatAggregate on Table API
> --------------------------------------------------------------------
>
>                 Key: FLINK-12794
>                 URL: https://issues.apache.org/jira/browse/FLINK-12794
>             Project: Flink
>          Issue Type: Sub-task
>          Components: Table SQL / API
>    Affects Versions: 1.9.0
>            Reporter: sunjincheng
>            Assignee: Hequn Cheng
>            Priority: Major
>              Labels: pull-request-available, stale-assigned
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> Since the execution of the Stream operator has two modes, `ACC` and 
> `ACCRetract`, users can achieve better performance by implementing special 
> interfaces for streaming. The table below is a quick summary.
> | |emitValue|emitUpdateWithRetract|emitUpdateWithoutRetract|
> |ACC|Y|N|Y|
> |ACCRetract|Y|Y|N|
>  * emitValue - for batch and streaming.
>  * eimitUpdateWithRetract - only for streaming in ACC mode(need key 
> definition on TableAggregateFunction, [under 
> discussion|https://docs.google.com/document/d/183qHo8PDG-xserDi_AbGP6YX9aPY0rVr80p3O3Gyz6U/edit?usp=sharing]).
>  * emitUpdateWithoutRetract - only for streaming in ACCRetract mode.
>  In this Jira we will add the ACC mode support for non-window streaming 
> FlatAggregate. the detail can be found in 
> [Flip-29|https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=97552739]



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

Reply via email to