You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2017/01/12 11:16:51 UTC
[jira] [Commented] (FLINK-5406) add normalization phase for
predicate logical plan rewriting between decorrelate query phase and
volcano optimization phase
[ https://issues.apache.org/jira/browse/FLINK-5406?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15820769#comment-15820769 ]
ASF GitHub Bot commented on FLINK-5406:
---------------------------------------
GitHub user godfreyhe opened a pull request:
https://github.com/apache/flink/pull/3101
[FLINK-5406] [table] add normalization phase for predicate logical plan rewriting
Normalization phase is for predicate logical plan rewriting and is independent of cost module. The rules in normalization phase do not need to repeatedly applied to different logical plan which is different to volcano optimization phase. And the benefit of normalization phase is to reduce the running time of volcano planner.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/godfreyhe/flink master
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/flink/pull/3101.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #3101
----
commit c9f11e7c38f921a403b56a5c124974eb66bddcac
Author: godfreyhe <go...@163.com>
Date: 2017-01-12T10:42:49Z
add normalization phase for predicate logical plan rewriting
----
> add normalization phase for predicate logical plan rewriting between decorrelate query phase and volcano optimization phase
> ---------------------------------------------------------------------------------------------------------------------------
>
> Key: FLINK-5406
> URL: https://issues.apache.org/jira/browse/FLINK-5406
> Project: Flink
> Issue Type: New Feature
> Components: Table API & SQL
> Reporter: godfrey he
> Assignee: godfrey he
>
> Normalization phase is for predicate logical plan rewriting and is independent of cost module. The rules in normalization phase do not need to repeatedly applied to different logical plan which is different to volcano optimization phase. And the benefit of normalization phase is to reduce the running time of volcano planner.
> *ReduceExpressionsRule* can apply various simplifying transformations on RexNode trees. Currently, there are two transformations:
> 1) Constant reduction, which evaluates constant subtrees, replacing them with a corresponding RexLiteral
> 2) Removal of redundant casts, which occurs when the argument into the cast is the same as the type of the resulting cast expression
> the above transformations do not depend on the cost module, so we can move the rules in *ReduceExpressionsRule* from DATASET_OPT_RULES/DATASTREAM_OPT_RULES to DataSet/DataStream Normalization Rules.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)