[
https://issues.apache.org/jira/browse/CALCITE-2973?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lai Zhou updated CALCITE-2973:
------------------------------
Description:
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 bring
a lot of benefits .
was:
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 support merge-join or hash-join rule for a theta join, it will
bring a lot of benefits .
> Make EnumerableMergeJoinRule to support a theta join
> ----------------------------------------------------
>
> 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
>
> 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
> bring a lot of benefits .
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
