Naming rules inconsistencies
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 1.1k
- Forks
- 232
- PR merge metrics
- No merged PRs in 30d
Description
Hello all,
Here's the situation. Apache Avro [spec has some naming guidelines](https://avro.apache.org/docs/1.11.1/specification/#names) for `Record, enums and fixed`. This library correctly checks that and fails when a file has a badly named field.
However, the official Avro library does not 😢
`avro-tools tojson ` happily reads the file (same goes for AWS - I think that's because they use Java)
There is a discussion about it [here](https://lists.apache.org/thread/39v98os6wdpyr6w31xdkz0yzol51fsrr) in the mailing list, and
furthermore Python seems to have [chosen to allow for disabling this validation](https://github.com/apache/avro/pull/1995)
Because of that last note, I think we should consider adding this optional functionality in this library too. What do you think? I can do a PR if you're on board.
Contributor guide
No contributing guide indexed for this repository
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 reading the linked Avro naming specification, mailing-list discussion, and Apache Avro Python change, then compare them with goavro's current validation behavior. Done means the library can optionally disable naming validation while retaining the current default behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- data-engineering
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100