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
It doesn't seem that field name aliases are supported? For example, if my avro definition has a field defined as:
{ "name": "plain_field", "type": [ "null", "double" ], "doc": "Any field", "default": null, "aliases": [ "alias_for_that_field" ] }
the resulting class does have a getPlainField() but does not have a getAliasForThatField() method.
getPlainField()
getAliasForThatField()
The text was updated successfully, but these errors were encountered:
That is not how aliases work. It accepts incoming data that has a field alias_for_that_field instead of plain_field.
alias_for_that_field
plain_field
Sorry, something went wrong.
No branches or pull requests
It doesn't seem that field name aliases are supported? For example, if my avro definition has a field defined as:
the resulting class does have a
getPlainField()
but does not have agetAliasForThatField()
method.The text was updated successfully, but these errors were encountered: