[fast-avro] Automatically degrade to use vanilla Avro if some new features are not supported in fast-avro
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 87
- Forks
- 73
- Avg merge
- 2h 50m
- Merged PRs (30d)
- 1
Description
Logical Types feature is not supported in fast-avro, and this was introduced by Avro-1.8.
When fast-avro processes the schemas using logical types, they will be ignored, which would cause the type mismatch problem on client side.
To solve this issue, fast-avro should degrade to vanilla Avro automatically when detecting the un-supported features in the schema definition instead of ignoring them blindly.
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
Start by tracing fast-avro's schema processing for logical types and comparing it with vanilla Avro behavior. Determine how unsupported schema features are detected and verify that processing falls back to vanilla Avro rather than silently ignoring them, preventing client-side type mismatches.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- data-engineering
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100