AsyncAPI.NET
AsyncAPI.NET copied to clipboard
Avro implementation does not support using defined named types
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.