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

["Lai Zhou (JIRA)" <ji...@apache.org>]

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

Lai Zhou edited comment on CALCITE-2973 at 5/15/19 3:13 AM:
------------------------------------------------------------

[~rubenql], now the inner join with a remainCondtion won't be converted to an inner-join plus a filter , the Enumerable(Hash)Join can handle it in a generic way.


was (Author: hhlai1990):
[~rubenql], now the inner join with a remainCondtion won't be converted to an inner-join and a filter , the Enumerable(Hash)Join can handle 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
>             Fix For: 1.20.0
>
>          Time Spent: 3h 50m
>  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
(v7.6.3#76005)