[ 
https://issues.apache.org/jira/browse/AVRO-2687?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17016905#comment-17016905
 ] 

Elliotte Rusty Harold edited comment on AVRO-2687 at 1/16/20 1:08 PM:
----------------------------------------------------------------------

Coincidentally the previous issue filed in this repo appears to be 
[https://issues.apache.org/jira/browse/AVRO-2682https://issues.apache.org/jira/projects/AVRO/issues/AVRO-2682?filter=allopenissues|https://issues.apache.org/jira/projects/AVRO/issues/AVRO-2682?filter=allopenissues]

 

and I see in the comments, "the right solution is to ensure that the version of 
Avro generating code is the same as the version used at runtime."

 

That doesn't seem appropriate for a serialization format which should not 
depend on the runtime classpath.

 

 


was (Author: elharo):
Coincidentally the last issue filed in this repo appears to be 
[https://issues.apache.org/jira/projects/AVRO/issues/AVRO-2682?filter=allopenissues]

 

and I see in the comments, "the right solution is to ensure that the version of 
Avro generating code is the same as the version used at runtime."

 

That doesn't seem appropriate for a serialization format which should not 
depend on the runtime classpath.

 

 

> Semantic Verisoning
> -------------------
>
>                 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)

Reply via email to