[jira] [Commented] (CALCITE-500) Ensure EnumerableJoin hashes the smallest input

["Atri Sharma (JIRA)" <ji...@apache.org>]

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

Atri Sharma commented on CALCITE-500:
-------------------------------------

PR:

[https://github.com/apache/calcite/pull/691]

 

[~julianhyde] [~vladimirsitnikov] Please take a look and let me know. I tested and saw that for inner joins, the smaller side is being built and the larger side is being probed.

 

Please see and let me know

> 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
>         Attachments: lookup.png
>
>
> {{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
(v7.6.3#76005)