[
https://issues.apache.org/jira/browse/CALCITE-500?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16070550#comment-16070550
]
Julian Hyde commented on CALCITE-500:
-------------------------------------
No unit tests, but it's widely used by the test suite. Run CalciteSuite in a
debugger and put a breakpoint in EnumerableJoin.implement and you'll see.
> Ensure EnumerableJoin hashes the smallest input
> -----------------------------------------------
>
> Key: CALCITE-500
> URL: https://issues.apache.org/jira/browse/CALCITE-500
> Project: Calcite
> Issue Type: Bug
> Affects Versions: 1.0.0-incubating
> Reporter: Vladimir Sitnikov
> Assignee: Atri Sharma
> Labels: newbie
>
> {{EnumerableJoin}} tries to put the smallest input the first, however when it
> comes to execution, Calcite creates lookup for _second_ input of join.
> It would be nice to ensure the lookup is created on the smallest input.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
