HolderCoder should be a StandardCoder and not a CustomCoder
Open
backward-incompatible
bug
core
java
P3
- Dominant language
- Java
- Stars
- 8.7k
- Forks
- 4.7k
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 205
Description
The issue is that the coder does not report component encodings which prevents effective runner inspection of the components.
Imported from Jira [BEAM-464](https://issues.apache.org/jira/browse/BEAM-464). Original Jira may contain additional context.
Reported by: lcwik.
Contributor guide
Research direction
Start by locating HolderCoder and the StandardCoder and CustomCoder definitions in the Apache Beam codebase, then trace how runner inspection obtains component encodings. Done means HolderCoder reports its component encodings through the StandardCoder path rather than the CustomCoder path; the issue names no specific tests, so identify the relevant coder or runner-inspection tests while investigating.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- data-engineering
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100