Naming rules inconsistencies #286
Comments
gannett-ggreer
added a commit
to GannettDigital/linkedin_goavro
that referenced
this issue
Dec 7, 2024
Some of our Avro schemas are generated with "invalid" names and this library refuses to accept them. That would be fine if it was only on writing an Avro schema with such fields but it also refuses to read any Avro schema, which is highly annoying. See also linkedin#286
gannett-ggreer
added a commit
to GannettDigital/linkedin_goavro
that referenced
this issue
Dec 7, 2024
Some of our Avro schemas are generated with "invalid" names and this library refuses to accept them. That would be fine if it was only on writing an Avro schema with such fields but it also refuses to read any Avro schema, which is highly annoying. See also linkedin#286
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hello all,
Here's the situation. Apache Avro spec has some naming guidelines 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 <badly-named-file.ocf>happily reads the file (same goes for AWS - I think that's because they use Java)There is a discussion about it here in the mailing list, and
furthermore Python seems to have chosen to allow for disabling this validation
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.
The text was updated successfully, but these errors were encountered: