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 (5,739 stars) (1,048 forks)batch import
enhancementfix-it-weekgood first issue

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

Tech stack
java
Domain
backenddatabase
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.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
Javaunderstanding of join types
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
40
Research direction
Investigate the execution plan schema in the KSQL codebase, likely in the `execution` or `schema` package. Identify which join types are currently using a broad enum and determine the strictest enum for each. Update the enum definitions and corresponding usages. Reference: issue #4223.