You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Looks like Avro backend is missing one crucial capability indicator, needed for (de)serializers to know that binary data can be handled natively.
Adding this should allow for (more) efficient serialization of java.util.UUID, for example.
Binary data reads/writes themselves are probably not affected since there are separate methods: this has more to do with binary representation of types like UUID.
The text was updated successfully, but these errors were encountered:
Note: looks like Schema generation for UUID type just indicates String, and does not have good access to find out if binary available, or, if it did, way to indicate that.
Will probably need to add something in schema interfaces for jackson-core, too, but can't use that in 2.10 regardless, so need to add a work-around in Avro schema handler.
Looks like I may have to leave default UUID serialization, schema type, as String for 2.10, and add some low-level support to be able to fix this in 2.11.
cowtowncoder
changed the title
Add AvroGenerator.canWriteBinaryNatively() to support binary writes
Add AvroGenerator.canWriteBinaryNatively() to support binary writes, fix java.util.UUID representation
Nov 27, 2019
Looks like Avro backend is missing one crucial capability indicator, needed for (de)serializers to know that binary data can be handled natively.
Adding this should allow for (more) efficient serialization of
java.util.UUID
, for example.Binary data reads/writes themselves are probably not affected since there are separate methods: this has more to do with binary representation of types like UUID.
The text was updated successfully, but these errors were encountered: