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
{{ message }}
This repository has been archived by the owner on Jan 22, 2019. It is now read-only.
Values whose byte-lengths are constant are more efficiently to packed in avro as "fixed" fields, because this encoding saves the overhead of a length-prefix. UUIDs and MD5/SHA hashes are common examples where this encoding can be beneficial.
The AvroSchemaGenerator does not currently support this field-type; it just treats byte[]/ByteBuffer fields as length-prefixed "bytes" fields.
Supporting "fixed" will likely involve some sort of annotation in the POJO to specify both the length and "name" of the generated datatype (note that "name" is currently required, for some reason, for every fixed type).
The text was updated successfully, but these errors were encountered:
Values whose byte-lengths are constant are more efficiently to packed in avro as "fixed" fields, because this encoding saves the overhead of a length-prefix. UUIDs and MD5/SHA hashes are common examples where this encoding can be beneficial.
The AvroSchemaGenerator does not currently support this field-type; it just treats byte[]/ByteBuffer fields as length-prefixed "bytes" fields.
Supporting "fixed" will likely involve some sort of annotation in the POJO to specify both the length and "name" of the generated datatype (note that "name" is currently required, for some reason, for every fixed type).
The text was updated successfully, but these errors were encountered: