[
https://issues.apache.org/jira/browse/FLINK-3503?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15196355#comment-15196355
]
ASF GitHub Bot commented on FLINK-3503:
---------------------------------------
GitHub user fhueske opened a pull request:
https://github.com/apache/flink/pull/1798
[FLINK-3503] [tableAPI] Add cost model for DataSet RelNodes to improve plan
selection
Calcite's default cost model does not take IO and CPU into account. As a
consequence, projections are not pushed down (as described in FLINK-3503).
This PR adds a basic cost model to push filters and projections towards the
sources.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/fhueske/flink tableRules
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/flink/pull/1798.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 #1798
----
commit 257b6b0162c4f426042bbbb6f9bb4812dc8a4e81
Author: Fabian Hueske <[email protected]>
Date: 2016-03-14T18:57:53Z
[FLINK-3503] [tableAPI] Add cost model for DataSet RelNodes to improve plan
selection.
----
> ProjectJoinTransposeRule fails to push down project.
> ----------------------------------------------------
>
> Key: FLINK-3503
> URL: https://issues.apache.org/jira/browse/FLINK-3503
> Project: Flink
> Issue Type: Improvement
> Components: Table API
> Reporter: Chengxiang Li
> Priority: Minor
>
> {noformat}
> val ds1 = CollectionDataSets.getSmall3TupleDataSet(env).as('a, 'b, 'c)
> val ds2 = CollectionDataSets.get5TupleDataSet(env).as('d, 'e, 'f, 'g, 'h)
> val joinT = ds1.join(ds2).where('b === 'e).select('c, 'g)
> {noformat}
> For this query, ProjectJoinTransposeRule should pushes a Project past a Join
> by splitting the projection into a projection on top of each child of the
> join.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
