Avro test doesn't take optionality into account. Unfair?

RameshRaj / thrift-protobuf-compare

Automatically exported from code.google.com/p/thrift-protobuf-compare

0 stars 0 forks source link

Avro test doesn't take optionality into account. Unfair? #21

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago

The Avro schema doesn't account for optionality of fields.  Since most of
the fields are defined to be optional, this yields significant space and
speed benefits (since Avro's binary format doesn't include tags like
Thrift/Protobuf).

When I use a schema that supports optionality, the serialized data size
increases by about 10% and serialization/deserialization time increases by
about 50%.

Original issue reported on code.google.com by kannan%c...@gtempaccount.com on 22 Feb 2010 at 5:10

GoogleCodeExporter commented 8 years ago

Attached the updated schema.

Original comment by kannan%c...@gtempaccount.com on 22 Feb 2010 at 5:11

Attachments:

Schema.json

GoogleCodeExporter commented 8 years ago

The "java (externalizable)" tests also has this issue.  It assumes that all 
fields
will be present.

Original comment by kannan%c...@gtempaccount.com on 23 Feb 2010 at 10:12