Details
-
Improvement
-
Status: Closed
-
Major
-
Resolution: Fixed
-
1.19.0
Description
The existing join-like (Join, SemiJoin, Correlate, etc.) logical and physical relational expressions have a few design issues which make some parts of the codebase complicated and difficult to understand.
The goal of this ticket is to improve the design of the respective expressions based on the discussion in the dev list (see thread Join, SemiJoin, Correlate).
Attachments
Issue Links
- Blocked
-
CALCITE-3036 Remove correlate variables from Join
- Closed
-
CALCITE-2973 Allow theta joins that have equi conditions to be executed using a hash join algorithm
- Closed
- causes
-
CALCITE-4819 SemiJoin operator is not skipped in materialized view-based rewriting algorithm
- Closed
- contains
-
CALCITE-3037 Rename EnumerableThetaJoin to EnumerableNestedLoopJoin
- Resolved
- is related to
-
CALCITE-3089 Deprecate EquiJoin
- Closed
-
CALCITE-4623 SemiJoinRule should not match SEMI join
- Closed
-
CALCITE-3133 Remove completely SemiJoinType
- Closed
- relates to
-
CALCITE-3102 Deprecation warnings following [CALCITE-2969]
- Closed
-
CALCITE-2857 Complicated plan generated for subuqery with both equi and non-equi condition
- Open
- supercedes
-
CALCITE-2968 New AntiJoin relational expression
- Closed
- links to