Skip to content

Avro implementation does not support defined named types #9

@VisualBean

Description

@VisualBean

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.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions