[
https://issues.apache.org/jira/browse/CALCITE-500?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladimir Sitnikov closed CALCITE-500.
-------------------------------------
Resolution: Fixed
Closing the issue as executor has to be consistent with optimizer.
Optimizer assumes the left collation is intact, so we can't just use another
input for building the hash table.
> 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
> Priority: Major
> Labels: newbie, pull-request-available
> Attachments: lookup.png
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> {{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
(v8.3.4#803005)
