Skip to content
Discussion options

You must be logged in to vote

Hmm, Thanks for the quick reply @jochenchrist

On AVRO it behaves more or less like a JSON oneof. A record can have one of multiple possible types. The message then specifies the name of the type to consider.

I have a fork of repo where I'm having some tweaks to write/read the avro. And I was thinking about a data contract customization to try accomodate such scenario.

Replies: 1 comment 1 reply

Comment options

You must be logged in to vote
1 reply
@samuelramos
Comment options

Answer selected by samuelramos
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
2 participants