confluentinc/ksql

Drop title fields from execution plan schema

Open

#4,222 opened on Jan 6, 2020

View on GitHubContributor guide
 (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
 (PR metrics pending)

Description

We should drop the title fields from the execution plan schema, since they aren't really needed.

Contributor guide

Research direction
Locate the execution plan schema definition in the codebase and remove the title fields. Ensure no other components depend on these fields.
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.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
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
JavaGit
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
75