linkedin
Fast-avro should support enum default value with avro-1.9+
Right now, Fast-avro is not respecting the enum default value for all avro versions, which is not right. This issue is used to track the enum default value support for avro-1.9+.
we could do better - fast-avro could honor default values under any avro (at least as a config somewhere) under 1.9+ it woudl be required to be more compatible in behaviour with native avro
I was thinking about that as well... maybe we ought to be have the 1.9 behavior across all versions. The only catch is that there is a warm up phase, and until it's complete, we call regular (well, mostly regular) Avro instead... so that means there could be brief periods of time where the pre-1.9 behavior shows up, which is less than ideal.
if i had to guess i'd say 99% of users would be fine with blocking until a codec class is ready. maybe we could also change behaviour there (make use-vanilla-until-warmup an opt-in)
Not quite sure on this.. Sometimes, the warm-up could take 10+ seconds for a large schema. And until now, we are trying to keep the same behavior between fast-avro and the vanilla avro to make sure there is no surprise when the users switch between them.