Details
-
New Feature
-
Status: Closed
-
Minor
-
Resolution: Fixed
-
1.19.0
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 improve the performance greatly.
Attachments
Issue Links
- Blocked
-
CALCITE-2969 Improve design of join-like relational expressions
- Closed
- is a parent of
-
CALCITE-3284 Enumerable hash semijoin / antijoin support non-equi join conditions
- Closed
- is related to
-
CALCITE-3089 Deprecate EquiJoin
- Closed
- relates to
-
CALCITE-2592 EnumerableMergeJoin is never taken
- Closed
-
CALCITE-2898 RelOptUtil#splitJoinCondition must consider RexFieldAccess referencing RexInputRef
- Closed
-
CALCITE-3285 EnumerableMergeJoin should support non-equi join conditions
- Closed
-
CALCITE-3535 EnumerableJoinRule: remove unnecessary Filter on top of INNER Join
- Closed
- links to