avro-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Lewis John Mcgibbney <lewis.mcgibb...@gmail.com>
Subject Re: Adding Conclusion to Avro Spec
Date Tue, 30 Sep 2014 15:21:57 GMT
Hi Doug,
Thanks for reply... I understand that I am here :)
Exactly what you've included within your reply would add value to the spec
If we could get that in there it would be great. This information is
utterly implicit to an outsider/new user.

On Monday, September 29, 2014, Doug Cutting <cutting@apache.org> wrote:

> On Sat, Sep 27, 2014 at 9:20 PM, Lewis John Mcgibbney
> <lewis.mcgibbney@gmail.com <javascript:;>> wrote:
> > Is there a possibility that someone can add material on how static the
> > specification documentation is
> Minor versions are meant to have back-compatible APIs and both back-
> and forward-compatible data formats.  Since the specification
> primarily concerns data formats, it's pretty stable.  In particular,
> every schema since 1.0 can be parsed by every 1.x release and every
> datum serialized since 1.0 should be readable by every 1.x release.
> We broke this policy once, in 1.3, which incompatibly altered the Avro
> file format.  I doubt we'll break it again.  Any further changes to
> forward or backward data compatibility would require a 2.0 release.
> > where people should go if they find
> > something wrong/require more clarification about, etc.
> You're there!
> This information could be included in the specification.  My instinct
> is to add it at the start, rather than the end, but I don't feel too
> strongly about that.
> Doug


View raw message