flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From GitBox <...@apache.org>
Subject [GitHub] [flink] wuchong opened a new pull request #8202: [FLINK-12133] [table-runtime-blink] Support unbounded aggregate in streaming table runtime
Date Thu, 18 Apr 2019 04:23:12 GMT
wuchong opened a new pull request #8202: [FLINK-12133] [table-runtime-blink] Support unbounded
aggregate in streaming table runtime
URL: https://github.com/apache/flink/pull/8202
 
 
   
   ## What is the purpose of the change
   
   This ticket is aiming to support unbounded aggregate in blink streaming runtime. Includes:
   
   1. GroupAggFunction: function that support unbounded aggregate without minibatch optimizations
   2. MiniBatchGroupAggFunction: function that support unbounded aggregate with minibatch
optimization
   3. MiniBatchLocalGroupAggFunction & MiniBatchGlobalGroupAggFunction: function that
support unbounded aggregate with local combine optimization
   4. MiniBatchIncrementalAggFunction: agg function with incremental optimization.
   
   
   ## Brief change log
   
    - Add `GroupAggFunction`, `MiniBatchGroupAggFunction`, `MiniBatchLocalGroupAggFunction`,
`MiniBatchIncrementalAggFunction`.
    - Move `TableConfig`, `MapView`, `ListView` to `flink-table-runtime-blink` module to make
runtime class can access them. They should be in api module at last. So this is a temporary
change.
    - Implement Expand and Union for runtime.
    - Introduce `StateDataViewStore` for `AggsHandleFunction` to access state DataView instead
of using `ExecutionContext` in it.
    - Introduce `SINGLE_VALUE` and `COLLECT` agg call.
    - Rewrite `MaxWithRetract`, `MinWithRetract`, `ConcatWithRetract`, `ConcatWsWithRetract`.
    - Fix several bugs in code generation and serialization and other places.
   
   ## Verifying this change
   
   - Add `AggregateITCase` with 6 modes to cover unbounded aggregates.
   - Add `SplitAggregateITCase` with 4 modes to cover distinct aggregates split optimization.
   
   
   ## Does this pull request potentially affect one of the following parts:
   
     - Dependencies (does it add or upgrade a dependency): (no)
     - The public API, i.e., is any changed class annotated with `@Public(Evolving)`: (no)
     - The serializers: (no)
     - The runtime per-record code paths (performance sensitive): (no)
     - Anything that affects deployment or recovery: JobManager (and its components), Checkpointing,
Yarn/Mesos, ZooKeeper: (no)
     - The S3 file system connector: (no)
   
   ## Documentation
   
     - Does this pull request introduce a new feature? (no)
     - If yes, how is the feature documented? (not applicable)
   

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services

Mime
View raw message