[
https://issues.apache.org/jira/browse/FLINK-5256?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15761698#comment-15761698
]
Anton Mushin commented on FLINK-5256:
-------------------------------------
Hi [~fhueske],
Where did you get the plan?
i tried execute your query in flink and got next plan:
{noformat}
DataSetCalc(select=[b, EXPR$1])
DataSetSingleRowJoin(where=[>(EXPR$1, EXPR$0)], join=[b, EXPR$1, EXPR$0],
=[NestedLoopJoin])
DataSetAggregate(groupBy=[b], select=[b, SUM(a) AS EXPR$1])
DataSetScan(table=[[_DataSetTable_0]])
DataSetCalc(select=[*($f0, 0.1) AS EXPR$0])
DataSetAggregate(select=[SUM(a) AS $f0])
DataSetUnion(union=[a])
DataSetValues(tuples=[[{ null }]], values=[a])
DataSetCalc(select=[a])
DataSetScan(table=[[_DataSetTable_0]])
{noformat}
Could you more detailed explain what is plan expected for your query if
{{DataSetSingleRowJoin}} will support outer joins?
> Extend DataSetSingleRowJoin to support Left and Right joins
> -----------------------------------------------------------
>
> Key: FLINK-5256
> URL: https://issues.apache.org/jira/browse/FLINK-5256
> Project: Flink
> Issue Type: Improvement
> Components: Table API & SQL
> Affects Versions: 1.2.0
> Reporter: Fabian Hueske
>
> The {{DataSetSingleRowJoin}} is a broadcast-map join that supports arbitrary
> inner joins where one input is a single row.
> I found that Calcite translates certain subqueries into non-equi left and
> right joins with single input. These cases can be handled if the
> {{DataSetSingleRowJoin}} is extended to support outer joins on the
> non-single-row input, i.e., left joins if the right side is single input and
> vice versa.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
