I am not an Avro expert, but here are some thoughts:
In general, I think you should submit a PR or PRs to suggest improvements,
unless you are unsure what change should be made. That seems more productive
than a list of things that you think are "stupid".
Another possibility would be putting to
Hi Askar
This is certainly an extensive list. I wanted to email you just to let you
know that *someone* has seen it. Though I can't speak to all of it, I do
have a few of my own impressions:
> How it is happened that such good format has so bad spec? How it is
happened that *best* format for this
Hi. I'm writing my own Avro implementation in Rust for personal use. During
this work I found a lot of issues in Avro
spec (the list follows).
I send this mail not only to user and dev mailing lists of Avro, but also to
Apache community list, Kafka list and 3
semi-randomly chosen Materialize e
