You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@flink.apache.org by "Kurt Young (JIRA)" <ji...@apache.org> on 2019/01/30 10:15:00 UTC

[jira] [Closed] (FLINK-9997) Improve Expression Reduce

     [ https://issues.apache.org/jira/browse/FLINK-9997?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Kurt Young closed FLINK-9997.
-----------------------------
    Resolution: Unresolved

> Improve Expression Reduce
> -------------------------
>
>                 Key: FLINK-9997
>                 URL: https://issues.apache.org/jira/browse/FLINK-9997
>             Project: Flink
>          Issue Type: Improvement
>          Components: Table API &amp; SQL
>            Reporter: Ruidong Li
>            Assignee: Ruidong Li
>            Priority: Major
>              Labels: pull-request-available
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> 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)