As others have noted, the data format has not changed and should be compatible.
The performance difference you note is curious. I wonder if this
could be related to the following issue?
https://issues.apache.org/jira/browse/AVRO-1348
You could try the 1.7.6 release candidate to test this:
There is at least one API incompatibility, which I learned when using
Voldemort.
https://github.com/voldemort/voldemort/pull/137
And from memory, there was a bug when using enum with 1.4 but I can't
remember exactly what.
Bertrand
Bertrand Dechoux
On Wed, Jan 22, 2014 at 5:36 PM, Arvind Kalya
As far as compatibility goes, the serialized format is 100% compatible. We
are actually using 1.4.1 to serialize and 1.7.5 to deserialize and it has
been working without surprises so far.
On Wed, Jan 22, 2014 at 8:29 AM, Jun Rao wrote:
> Hi,
>
> We are on Avro 1.4.0 and plan to upgrade to Avro
Hi,
We are on Avro 1.4.0 and plan to upgrade to Avro 1.7.5. Is the binary
encoding 100% compatible btw the 2 versions? Also, I did some perf testing
and it seems that on average, 1.7.5 is about 6% faster on encoding and 20%
slower on decoding compared with 1.4.0. Is the degradation on decoding
per
