[
https://issues.apache.org/jira/browse/AVRO-2687?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17017798#comment-17017798
]
Fokko Driesprong commented on AVRO-2687:
----------------------------------------
So we're trying to maintain compatibility in a semantic versioning way as well.
Sean did a compatibility report on it as well:
[http://people.apache.org/~busbey/avro/1.9.0-RC4/1.8.2_to_1.9.0RC4_compat_report.html]
However, we've removed some Jackson stuff from the public API that we wanted to
get rid of. There are some sharp edges on the 1.9 release, and Joda is still
available by setting a configuration.
I believe [~iemejia] was working on updating Avro in beam as well.
> Semantic Versioning
> -------------------
>
> Key: AVRO-2687
> URL: https://issues.apache.org/jira/browse/AVRO-2687
> Project: Apache Avro
> Issue Type: Improvement
> Reporter: Elliotte Rusty Harold
> Priority: Major
>
> API level and other incompatibility between Avro minor versions is causing
> significant problems for Apache Beam. E.g.
> [https://github.com/apache/beam/pull/9779]
>
> Stable releases that don't break backwards compatibility would help us and
> other users a great deal. E.g. not removing joda.time support in 1.10.
>
> Absent that, at a minimum Avro should update its major version for any API
> breaking change. E.g. 1.9 should have been 2.0 because it was not API
> compatible with 1.8. In the case of Avro, this would apply not just to the
> public Java API but also to the serialization format.
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
