[ 
https://issues.apache.org/jira/browse/FLINK-9997?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16571818#comment-16571818
 ] 

Ruidong Li commented on FLINK-9997:
-----------------------------------

Adding the Calc normalization to the logical optimization rules will cause a 
long-playing optimization,I'm trying to resolve it. 

> Improve Expression Reduce
> -------------------------
>
>                 Key: FLINK-9997
>                 URL: https://issues.apache.org/jira/browse/FLINK-9997
>             Project: Flink
>          Issue Type: Improvement
>          Components: Table API & SQL
>            Reporter: Ruidong Li
>            Assignee: Ruidong Li
>            Priority: Major
>              Labels: pull-request-available
>
> There's no Calc node at normalize plans, so ReduceExpressionRule.CALC does 
> not match any thing.
> If adding calc-related rules to normalize phase, then project-related rules 
> and filter-related rules do not match any thing at logical opt phase. If 
> adding ReduceExpressionRule.CALC to logical opt phase, it will increase the 
> the search time. Therefore, adding a new phase after logical opt may be an 
> option.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to