You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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)
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:
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: