[
https://issues.apache.org/jira/browse/AVRO-2687?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17046994#comment-17046994
]
Ismaël Mejía commented on AVRO-2687:
------------------------------------
I just crossed by chance the arrow versioning policy which separates format
from API so probably an approach worth exploring
[https://arrow.apache.org/docs/format/Versioning.html]
However I am still unconvinced that the effort is worth the benefits, we
already lack engineering resources in Avro and this sounds like a ton of extra
work and extra future work just to make the expectations of semantic versioning
happy. Maybe we just have to deal with the fact of being different, we will not
be the first or the last project to do it.
> 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)
