Hmmm. I am pretty conservative in not wanting to make any changes,
ever. That's the easiest way to offer great support between
artifacts, versions and languages!
For this example (extending the spec to permit JSON number and string
for floating point defaults), there's absolutely no impact on bi
Sounds like a reasonable spec change. I think this would be our first
breaking spec change? does that mean this is the time for us to hash
out versioning the spec, or are we going to update all of our versions
to 2.x?
Can we get an idea on failure expectations for the SDKs we maintain?
On Wed, Ju
Hello!
There's this problem and fix that would require a spec change:
https://issues.apache.org/jira/browse/AVRO-2858
Currently NaN and Infinity are valid IEEE 754 floating point values,
but only finite values are permitted in JSON numbers.
What do you think about encoding Avro numeric types ei
