Tatu Saloranta

@baharclerode I can do that too if there are no cases where lone `@Union` would be expected to work? I was assuming that value classes for `@Union` might include types...

Sounds good -- fix against 2.13 would be appreciated.

I would have thought that reading/deserialization should also work fine, as long as low-level decoder uses the schema information appropriately? Although I guess if this is not the case, then...

Schema is carried along when constructing readers/writers, so that'd be the place to store information. It has unfortunately been a while since I looked into this so I do not...

One possible way forward here would be a (unit) test that shows incorrect handling; possibly contrasting Avro-backed decoder (which would expect properly encoded/serialized value) to Jackson one (which works with...

Jackson requires logical property names to be used to match to Avro schema. But it is possible to both define safe property names with `@JsonProperty` (ones with no hyphens) and...

And this is with which Jackson version?

Ok. So reproduction is almost complete, one missing piece being the encoded input file. I think that is needed as presumably module would not write such content. I am guessing...

Yes, that does start with `Obj` signature indicating Object Container addition, with signature followed by JSON-encoded embedded schema. So as things are, Object Container files are not supported, only raw...

Ok. Just to make sure I understand this correctly, the concept of native type ids is somewhat orthogonal to `@JsonTypeInfo`: it was added after `@JsonTypeInfo` existed. Or maybe better way...