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.

Sign up for GitHub

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

Jump to bottom

Avro implementation does not support using defined named types #194

Open

VisualBean opened this issue Oct 10, 2024 · 0 comments

Collaborator

VisualBean commented Oct 10, 2024 •

edited

Loading

As defined in the specification under Schemas https://avro.apache.org/docs/1.9.0/spec.html#schemas
Using already defined names, should be supported.
This means that

{
  "type": "record",
  "name": "LongList",
  "aliases": ["LinkedLongs"],                      // old name for this
  "fields" : [
    {"name": "value", "type": "long"},             // each element has a long
    {"name": "next", "type": ["null", "LongList"]} // optional next element
  ]
}

is not supported in the current implementation, as "LongList" is a defined named type, but we dont deserialize it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment