[
https://issues.apache.org/jira/browse/FLINK-3226?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15134451#comment-15134451
]
ASF GitHub Bot commented on FLINK-3226:
---------------------------------------
GitHub user twalthr opened a pull request:
https://github.com/apache/flink/pull/1595
[FLINK-3226] Implement a CodeGenerator for an efficient translation to
DataSet programs
This PR implements a CodeGenerator for Table API on Calcite.
It includes the following:
- FilterITCase, SelectITCase and ExpressionITCase are mostly working again
- Null values are now fully supported and tested with new
`TableProgramsTestBase`
- Arithmetic `+-*/ +X -X`, logical operators `== != AND, OR, NOT, IS NULL,
NOT NULL` are supported.
- Logical operators implement 3-valued logic.
- A new configuration parameter `efficientTypeUsage` allows generated
DataSet programs to be as efficient as ordinary DataSet programs by avoiding
unnecessary type conversions and using most efficient type for every operator.
Limitations:
- String functions are not yet supported. They will be forwarded to
Calcites runtime functions once I have implemented the necessary interfaces for
that.
- Expression type casting is missing yet
- Date Literal is not supported yet
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/twalthr/flink CodeGen
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/flink/pull/1595.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 #1595
----
commit c1a63287de0014f0b5bd23d1e0bc31e679f02fbe
Author: twalthr <twal...@apache.org>
Date: 2016-02-05T16:40:54Z
[FLINK-3226] Implement a CodeGenerator for an efficient translation to
DataSet programs
----
> Translate optimized logical Table API plans into physical plans representing
> DataSet programs
> ---------------------------------------------------------------------------------------------
>
> Key: FLINK-3226
> URL: https://issues.apache.org/jira/browse/FLINK-3226
> Project: Flink
> Issue Type: Sub-task
> Components: Table API
> Reporter: Fabian Hueske
> Assignee: Chengxiang Li
>
> This issue is about translating an (optimized) logical Table API (see
> FLINK-3225) query plan into a physical plan. The physical plan is a 1-to-1
> representation of the DataSet program that will be executed. This means:
> - Each Flink RelNode refers to exactly one Flink DataSet or DataStream
> operator.
> - All (join and grouping) keys of Flink operators are correctly specified.
> - The expressions which are to be executed in user-code are identified.
> - All fields are referenced with their physical execution-time index.
> - Flink type information is available.
> - Optional: Add physical execution hints for joins
> The translation should be the final part of Calcite's optimization process.
> For this task we need to:
> - implement a set of Flink DataSet RelNodes. Each RelNode corresponds to one
> Flink DataSet operator (Map, Reduce, Join, ...). The RelNodes must hold all
> relevant operator information (keys, user-code expression, strategy hints,
> parallelism).
> - implement rules to translate optimized Calcite RelNodes into Flink
> RelNodes. We start with a straight-forward mapping and later add rules that
> merge several relational operators into a single Flink operator, e.g., merge
> a join followed by a filter. Timo implemented some rules for the first SQL
> implementation which can be used as a starting point.
> - Integrate the translation rules into the Calcite optimization process
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
