flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From GitBox <...@apache.org>
Subject [GitHub] [flink] godfreyhe opened a new pull request #8356: [FLINK-12424] [table-planner-blink] Supports dag (multiple-sinks query) optimization
Date Tue, 07 May 2019 06:01:53 GMT
godfreyhe opened a new pull request #8356: [FLINK-12424] [table-planner-blink] Supports dag
(multiple-sinks query) optimization
URL: https://github.com/apache/flink/pull/8356
 
 
   
   ## What is the purpose of the change
   
   *Supports dag (multiple-sinks query) optimization*
   
   
   ## Brief change log
   
     - *Add execute method in TableEnvironment to compile the multiple-sinks plan to transformations
and execute the job*
     - *Add implementation of explain method to display the multiple-sinks plan*
     - *Add RelNodeBlock to decompose the multiple-sinks plan to different block*
     - *Update Optimizer implementation to handle multiple-sinks optimization*
   
   
   ## Verifying this change
   
   
   This change added tests and can be verified as follows:
   
     - *Added ExplainTest to validate the explain result for different kind of queries*
     - *Added DagOptimizationTest to validate the optimized plan for different kind of queries*
   
   ## 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 documented)
   

----------------------------------------------------------------
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