[ 
https://issues.apache.org/jira/browse/FLINK-5255?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15734849#comment-15734849
 ] 

Fabian Hueske commented on FLINK-5255:
--------------------------------------

Initially, the plan consists of {{LogicalProject}} and {{LogicalFilter}}. These 
are converted into {{LogicalCalc}} by optimization rules. So, these plans are 
only available during optimization.

I assume you are looking at the plans produced by 
{{TableEnvironment.explain()}}. Until recently, explain only showed the 
pre-optimization plan and the physical DataSet program. Since a few days, it 
also shows the result of the optimization.
If you rebase your commit, explain should show you the result of the 
optimization ({{LogicalCalc}} will be translated into {{DataSetCalc}}).

> Improve single row check in DataSetSingleRowJoinRule
> ----------------------------------------------------
>
>                 Key: FLINK-5255
>                 URL: https://issues.apache.org/jira/browse/FLINK-5255
>             Project: Flink
>          Issue Type: Improvement
>          Components: Table API & SQL
>    Affects Versions: 1.2.0
>            Reporter: Fabian Hueske
>            Assignee: Alexander Shoshin
>
> {{DataSetSingleRowJoinRule}} checks converts an arbitrary inner join (cross, 
> theta, equi) where one input has exactly one row into a broadcast-map join.
> Currently, the condition to check for the single row is that the input of the 
> join must be a global aggregation. The check fails if the input is a 
> {{LogicalCalc}} followed by {{LogicalAggregate}}.
> Hence, the following query cannot be executed:
> {code}
> SELECT absum, x.a
> FROM x, (SELECT a.sum + b.sum AS absum FROM y)
> {code}
> The single row check should be extended to accept a {{LogicalCalc}} that has 
> no condition {{(RexProgram.getCondition() == null)}}.



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

Reply via email to