[
https://issues.apache.org/jira/browse/PARQUET-1295?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16480276#comment-16480276
]
Gabor Szadovszky commented on PARQUET-1295:
-------------------------------------------
[Here|https://github.com/apache/parquet-mr/blob/master/pom.xml#L246] starts a
lot of exclusions. That suggests there are many packages meant to be internal
even if they are public from java point of view. Unfortunately, we did not use
any other comment/annotation/package naming to inform the user which
class/method shall be used and which not.
To maintain backward compatibility from now on the best we can do is to remove
all the exclusions (except the ones that really make sense e.g. shaded
packages) and use the previous release all the time ({{1.10.0}} for now) for
the {{semver}} check. Unfortunately, we cannot do anything with the breaking
changes already released.
We also have to take care about the backward compatibility at review. Not only
public API changes can break backward compatibility but the actual behaviour of
the functions.
[~zi], [~rdblue], what do you think?
> 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)
