apache/beam

[Umbrella] Eliminate nullability errors from Beam Java

Open

#20,497 opened on Jun 4, 2022

View on GitHubContributor guide
 (1 comment) (0 reactions) (0 assignees)Java (4,097 forks)batch import
P3coregood first issueimprovementjava

Repository metrics

Stars
 (7,313 stars)
PR merge metrics
 (PR metrics pending)

Description

I enabled the checker framework and the core SDK exceeds 100 nullability errors immediately. We should make this number zero, since nullability errors are solved problem in computer science and they do periodically impact Beam.

Imported from Jira BEAM-10402. Original Jira may contain additional context. Reported by: kenn.

Contributor guide

Research direction
Enable the checker framework and systematically fix all nullability errors in the core SDK. Start by examining the nullability checker output and fixing errors one by one. Focus on common patterns like missing @Nullable annotations on method parameters or return types.
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.
1-2 days
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.
Mostly clear
Prerequisites
Javanullability annotations
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
30