You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@calcite.apache.org by "Julian Hyde (JIRA)" <ji...@apache.org> on 2014/12/01 18:55:13 UTC
[jira] [Commented] (CALCITE-500) Ensure EnumerableJoin hashes the
smallest input
[ https://issues.apache.org/jira/browse/CALCITE-500?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14230122#comment-14230122 ]
Julian Hyde commented on CALCITE-500:
-------------------------------------
Yes, my mistake. EnumerableJoin should build the left, probe the right. Hopefully costing has ensured that the left is smaller than the right, but EnumerableJoin should build the left regardless.
> 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: Julian Hyde
> 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.3.4#6332)