apache/beam

Eliminate rawtype errors from Beam Java

Open

#20,447 opened on Jun 4, 2022

View on GitHub
 (1 comment) (0 reactions) (1 assignee)Java (4,097 forks)batch import
P3amqpavroawsazurecassandraclickhouseelasticsearchfilesgcpgood first issuehadoop-file-systemimprovementiojava

Repository metrics

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

Description

A few modules used to have no rawtype errors. Now many of them do. Rawtypes are a legacy compatibility feature that should not be used in new code. Concretely, they obscure types (readability), mask errors (casts failing at runtime), and harm static analysis (checker framework recommends eliminating rawtypes as your first step)

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

Contributor guide

Research direction
Locate rawtype warnings in the codebase and replace them with proper generics.
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.
1
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
Java
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
80