Skip to content
New issue

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

Add support for aliases #21

Open
dansherpa opened this issue Jun 11, 2021 · 1 comment
Open

Add support for aliases #21

dansherpa opened this issue Jun 11, 2021 · 1 comment

Comments

@dansherpa
Copy link

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.

@eikemeier
Copy link

the resulting class does have a getPlainField() but does not have a getAliasForThatField() method.

That is not how aliases work. It accepts incoming data that has a field alias_for_that_field instead of plain_field.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants