You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Vasia Kalavri (JIRA)" <ji...@apache.org> on 2016/03/18 14:56:33 UTC

[jira] [Resolved] (FLINK-3225) Optimize logical Table API plans in Calcite

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

Vasia Kalavri resolved FLINK-3225.
----------------------------------
       Resolution: Implemented
    Fix Version/s: 1.1.0

> Optimize logical Table API plans in Calcite
> -------------------------------------------
>
>                 Key: FLINK-3225
>                 URL: https://issues.apache.org/jira/browse/FLINK-3225
>             Project: Flink
>          Issue Type: Sub-task
>          Components: Table API
>            Reporter: Fabian Hueske
>            Assignee: Fabian Hueske
>             Fix For: 1.1.0
>
>
> This task implements the optimization of logical Table API plans with Apache Calcite. The input of the optimization process is a logical query plan consisting of Calcite RelNodes. FLINK-3223 translates Table API queries into this representation.
> The result of this issue is an optimized logical plan.
> Calcite's rule-based optimizer applies query rewriting and optimization rules. For Batch SQL, we can use (a subset of) Calcite’s default optimization rules. 
> For this issue we have to 
> - add the Calcite optimizer to the translation process
> - select an appropriate set of batch optimization rules from Calcite’s default rules. We can reuse the rules selected by Timo’s first SQL implementation.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)