[
https://issues.apache.org/jira/browse/PARQUET-1295?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16483216#comment-16483216
]
Vlad Rozov commented on PARQUET-1295:
-------------------------------------
Parquet libraries do not follow proper semantic versioning as any outside
developer can't reliably say whether she is using API that is stable and is
subject of the semantic versioning or it is an internal API and an upgrade to a
newer version may require a significant code changes. Take a look at
{{org.apache.parquet.column.values.ValuesReader}}. Nothing in the package name,
class or method annotations suggests that it is an internal class that is not
subject of semantic versioning. That information is hidden somewhere in the pom
file. The class even has java documentation, that implies that it is not
"internal".
The same applies to classes and methods added since 1.7.0. How may an external
developer know that a new method added after 1.7.0 to a class that existed
before 1.7.0 is not subject of the semantic versioning and avoid using it?
> Parquet libraries do not follow proper semantic versioning
> ----------------------------------------------------------
>
> Key: PARQUET-1295
> URL: https://issues.apache.org/jira/browse/PARQUET-1295
> Project: Parquet
> Issue Type: Bug
> Reporter: Vlad Rozov
> Priority: Major
>
> There are changes between 1.8.0 and 1.10.0 that break API compatibility. A
> minor version change is supposed to be backward compatible with 1.9.0 and
> 1.8.0.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
