[
https://issues.apache.org/jira/browse/FLINK-3225?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15122644#comment-15122644
]
ASF GitHub Bot commented on FLINK-3225:
---------------------------------------
GitHub user fhueske opened a pull request:
https://github.com/apache/flink/pull/1559
[FLINK-3225] Implemented optimization of Table API queries via Calcite
- added logical Flink nodes and translation rules
- added stubs for DataSet translation rules
- ported DataSetNodes to Scala
- reactivated tests and added expected NotImplementedError
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/fhueske/flink calciteOpt
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/flink/pull/1559.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 #1559
----
commit 3fba706ab39e3fdb1d4c3b307a36a2184476a304
Author: Fabian Hueske <fhue...@apache.org>
Date: 2016-01-26T12:22:38Z
[FLINK-3225] Implemented optimization of Table API queries via Calcite
- added logical Flink nodes and translation rules
- added stubs for DataSet translation rules
- ported DataSetNodes to Scala
- reactivated tests and added expected NotImplementedError
----
> 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
>
> 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)
