We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
When java avro-tools convert .avdl files into .avsc files
the files are created with namespaces which aren't supported by pydantic-avro
https://avro.apache.org/docs/1.10.2/spec.html
this breaks classes when they are reused, as the key doesn't match
aka "<some_namespace>.Class" is stored in classes as "Class" instead of "<some_namespace>.Class"
written a small change when looking up a reused class will look at the Class portion of namespaced types
example
{ "name": "Test", "type": "record", "fields": [ { "name": "col1", "type": { "type": "record", "name": "Nested", "namespace": "com.pydantic", "fields": [{"name": "col1", "type": "string"}]}, }, { "name": "col2", "type": "com.pydantic.Nested", }, ], }
Note existing edge case where there is a clash with namespaces but that already exists for non reused case
The text was updated successfully, but these errors were encountered:
godatadriven#61 updating get_python_type to lookup class by final cla…
df3b66c
…ss name without namespace
No branches or pull requests
When java avro-tools convert .avdl files into .avsc files
the files are created with namespaces which aren't supported by pydantic-avro
https://avro.apache.org/docs/1.10.2/spec.html
this breaks classes when they are reused, as the key doesn't match
aka "<some_namespace>.Class" is stored in classes as "Class" instead of "<some_namespace>.Class"
written a small change when looking up a reused class will look at the Class portion of namespaced types
example
Note existing edge case where there is a clash with namespaces but that already exists for non reused case
The text was updated successfully, but these errors were encountered: