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

Posted to issues@calcite.apache.org by "Ruben Quesada Lopez (Jira)" <ji...@apache.org> on 2019/08/30 06:56:00 UTC

[jira] [Comment Edited] (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=16919273#comment-16919273 ] 

Ruben Quesada Lopez edited comment on CALCITE-2973 at 8/30/19 6:55 AM:
-----------------------------------------------------------------------

Fixed via https://github.com/apache/calcite/commit/6cec81178e6739d9b1f3474dc5dbd7488dda2464
Thanks for the PR [~hhlai1990]!


was (Author: rubenql):
Fixed via https://github.com/apache/calcite/commit/6cec81178e6739d9b1f3474dc5dbd7488dda2464
Thanks for the Pr [~hhlai1990]!

> 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.21.0
>
>          Time Spent: 9.5h
>  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)