Unify forked avro classes across helper module and fast-avro module
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 87
- Forks
- 73
- Avg merge
- 2h 50m
- Merged PRs (30d)
- 1
Description
There are multiple versions of "forked" avro classes
- there is a per-avro-version "forked" Symbol in each helper, with some modifications to support
- compatible json
- some caching optimization
- there is a backport Symbol used in fast-avro, also with some modifications
- it uses AvroCompatibilityHelper based on the backport avro 1.8 symbol
Helper module is meant to build the compatibility helper, in theory, all the backported classes should be in helper module if possible.
This will be a problem if fast-avro starts to support avro 1.9+
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Compare the forked Avro classes in the helper module with the backport Symbol and related classes in the fast-avro module. Trace how AvroCompatibilityHelper and the per-Avro-version helpers are built and used; done means the backported classes have one shared home and future Avro version support does not require duplicate implementations.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- tooling
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100