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
Currently, we raise an exception when a top-level schema or protocol just provides a name, not a namespace.
We assume that it is practical impossible to use the schema or protocol (especially when it comes to code generation) without a full-qualified name (namespace + name).
Idea: We could set a default namespace on parser/declaration level that is used when an avro file does not define its own namespace. This would prevent the exception.
The text was updated successfully, but these errors were encountered:
Currently, we raise an exception when a top-level schema or protocol just provides a name, not a namespace.
We assume that it is practical impossible to use the schema or protocol (especially when it comes to code generation) without a full-qualified name (namespace + name).
Idea: We could set a default namespace on parser/declaration level that is used when an avro file does not define its own namespace. This would prevent the exception.
The text was updated successfully, but these errors were encountered: