FasterXML / FasterXML/jackson-dataformats-binary
Consider rewriting Schema-compatibility verification (`SchemaCompatibility`)
Open
avro
- Dominant language
- Java
- Stars
- 347
- Forks
- 156
- Avg merge
- 3d 3h
- Merged PRs (30d)
- 22
Description
As per title: current verifier seems to both be overly sensitive (possibly false alerts) AND also does not indicate what exactly went wrong (just that it did). It should be possible to improve on this, rewrite the logic following the baseline checks but not necessarily implementation.
As an added bonus, it should be possible (if we choose to) run verifier for multiple issues, not just the first one.
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.