[
https://issues.apache.org/jira/browse/CALCITE-4812?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17422905#comment-17422905
]
Julian Hyde commented on CALCITE-4812:
--------------------------------------
I would like to see a test case also. Is it a case that can be represented in
{{class Join}} but cannot be created by {{RelBuilder.join}}?
If we have a correlated join (say "TABLE Emp" join "(SELECT * FROM Dept WHERE
deptno = $v1.deptno OR deptno = $v2.deptno)") and the user tries to create two
correlating variables $v1 and $v2 each referencing the left input to the join,
do we let them do that? Should we let them?
> RelBuilder.join should error multiple correlate ids
> ---------------------------------------------------
>
> Key: CALCITE-4812
> URL: https://issues.apache.org/jira/browse/CALCITE-4812
> Project: Calcite
> Issue Type: Improvement
> Reporter: James Starr
> Assignee: James Starr
> Priority: Major
>
> Relbuilder.join does not correctly handle multiple correlate ids. An error
> should be thrown when multiple ids are passed in.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
