apache/beam

Do not convert a join that we cannot support

Open

#18,277 opened on Jun 3, 2022

View on GitHub
 (0 comments) (0 reactions) (0 assignees)Java (4,097 forks)batch import
P3dslgood first issuesqlsub-task

Repository metrics

Stars
 (7,313 stars)
PR merge metrics
 (Avg merge 6d) (243 merged PRs in 30d)

Description

The BeamJoinRule matches all LogicalJoin operators. If we make it not match a full join then Calcite should look for a different plan when it converts to BeamLogicalConvention. That is a good step to make sure we can support things and also force the logical optimizer to choose non-full joins.

Imported from Jira BEAM-4439. Original Jira may contain additional context. Reported by: kenn. Subtask of issue #18276

Contributor guide

Research direction
Examine the BeamJoinRule implementation to understand how it matches LogicalJoin operators. Modify the rule to skip full joins, ensuring Calcite's optimizer finds an alternative plan for unsupported joins.
Tech stack
java
Domain
backend
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
JavaApache BeamCalcite
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
35