You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@calcite.apache.org by "Lai Zhou (Jira)" <ji...@apache.org> on 2019/08/22 02:36:00 UTC

[jira] [Commented] (CALCITE-2973) Allow theta joins that have equi conditions to be executed using a hash join algorithm

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

Lai Zhou commented on CALCITE-2973:
-----------------------------------

[~rubenql]， [~hyuan] ,[~julianhyde], [~danny0405], the pr is ready ,would someone help to review it ?

> Allow theta joins that have equi conditions to be executed using a hash join algorithm
> --------------------------------------------------------------------------------------
>
>                 Key: CALCITE-2973
>                 URL: https://issues.apache.org/jira/browse/CALCITE-2973
>             Project: Calcite
>          Issue Type: New Feature
>          Components: core
>    Affects Versions: 1.19.0
>            Reporter: Lai Zhou
>            Priority: Minor
>              Labels: pull-request-available
>          Time Spent: 4h 10m
>  Remaining Estimate: 0h
>
> Now the EnumerableMergeJoinRule only supports an inner and equi join.
> If users make a theta-join query  for a large dataset (such as 10000*10000), the nested-loop join process will take dozens of time than the sort-merge join process .
> So if we can apply merge-join or hash-join rule for a theta join, it will improve the performance greatly.



--
This message was sent by Atlassian Jira
(v8.3.2#803003)