linkedin / linkedin/avro-util

do not complain about single-arg DatumReader in generated classes

Open
#229 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement spotbugs
Dominant language
Java
Stars
87
Forks
73
Avg merge
2h 50m
Merged PRs (30d)
1

Description

otherwise it triggers on READER$ in generated specific record classes

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by locating the check that complains about single-argument DatumReader usage and inspect how it handles READER$ in generated specific record classes. Confirm the expected behavior for that generated pattern, then run the relevant existing tests or checks to verify that it no longer reports a complaint while other cases remain covered.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
backend
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.