flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kurt Young (JIRA)" <j...@apache.org>
Subject [jira] [Closed] (FLINK-12062) Introduce bundle operator to streaming table runtime
Date Wed, 03 Apr 2019 08:51:00 GMT

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

Kurt Young closed FLINK-12062.
       Resolution: Fixed
    Fix Version/s: 1.9.0

fixed in 1d5dda330ff61e66723ba3d98d38ba4642b8cd0d

> Introduce bundle operator to streaming table runtime
> ----------------------------------------------------
>                 Key: FLINK-12062
>                 URL: https://issues.apache.org/jira/browse/FLINK-12062
>             Project: Flink
>          Issue Type: Improvement
>          Components: Table SQL / Runtime
>            Reporter: Kurt Young
>            Assignee: Kurt Young
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 1.9.0
>          Time Spent: 10m
>  Remaining Estimate: 0h
> Bundle operator will try to save incoming records in a key-value map. Once bundler triggers,
the bundle function will be invoked. All buffered data will be passed in, and one can do some
optimizations based on this. 
> One useful scenario for bundle operator is "Group Aggregate". We can organize the bundle
data with grouping key. Once bundle triggers, we can first pre aggregate all data belongs
to same key in memory, then we only have to operate with state once for each key. This will
save lots of cost and have better performance.

This message was sent by Atlassian JIRA

View raw message