You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by GitBox <gi...@apache.org> on 2019/05/10 12:13:05 UTC

[GitHub] [flink] godfreyhe opened a new pull request #8411: [FLINK-12487] [table-planner-blink] Introduce planner rules to rewrite expression and merge calc

godfreyhe opened a new pull request #8411: [FLINK-12487] [table-planner-blink] Introduce planner rules to rewrite expression and merge calc
URL: https://github.com/apache/flink/pull/8411
 
 
   
   
   ## What is the purpose of the change
   
   *Introduce planner rules to rewrite expression and merge calc*
   
   
   ## Brief change log
   
     - *added ConvertToNotInOrInRule to convert a cascade of predicates to IN or NOT_IN*
     - *added RewriteCoalesceRule to rewrite Coalesce to Case When*
     - *added FlinkCalcMergeRule to simplify the merged program*
   
   
   ## Verifying this change
   
   This change added tests and can be verified as follows:
   
   *(example:)*
      - *Added ConvertToNotInOrInRuleTest that validates the plan after ConvertToNotInOrInRule is applied*
     - *Added RewriteCoalesceRuleTest that validates the plan after RewriteCoalesceRule is applied*
      - *Added FlinkCalcMergeRuleTest that validates the plan after FlinkCalcMergeRule is applied*
   
   ## 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