confluentinc/ksql

Use a more restricted enum for different join types in the execution plan schema

Open

#4,223 opened on Jan 6, 2020

View on GitHub
 (0 comments) (0 reactions) (1 assignee)Java (1,048 forks)batch import
enhancementfix-it-weekgood first issue

Repository metrics

Stars
 (5,739 stars)
PR merge metrics
 (Avg merge 4d 20h) (6 merged PRs in 30d)

Description

Currently all join types in the schema support OUTER/INNER/LEFT as join types. However, some joins don't support all the different join types. We should use the strictest possible enum for each join.

Contributor guide

Research direction
Examine the execution plan schema to identify each join type's allowed join types, then update the enum to restrict to the supported ones.
Tech stack
java
Domain
backend
Issue type
Refactor
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.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
JavaSQL
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
65