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, Jun 10, 2020 at 9:49 AM Ryan Skraba <r...@skraba.com> wrote: > > 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 either as a JSON > number or a JSON string? I think this is probably more in line with > the intention of default values than failing when "123.45" is > encountered, or excluding NaN / Infinity from possible default values. > > The consequence of making this official is that new schemas might > cause an existing SDK for a language to fail. I'm not sure this is > currently the case... to verify. > > Best regards, Ryan -- Sean
