[
https://issues.apache.org/jira/browse/PARQUET-1666?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17259933#comment-17259933
]
Gabor Szadovszky commented on PARQUET-1666:
-------------------------------------------
That's a good question. We've had a discussion a while ago. The conclusion was
that dropping a complete module is not a breaking change in the terms of
semantic versioning. We just say that we no longer develop them. If we keep
releasing parquet-mr in a binary compatible way (that's the plan) then any user
is able to use the old version of these modules with a newer parquet-mr release.
Meanwhile, if any contributor realize (because of the deprecation) there might
be improvements necessary in these modules we can undo the deprecation.
> Remove Unused Modules
> ----------------------
>
> Key: PARQUET-1666
> URL: https://issues.apache.org/jira/browse/PARQUET-1666
> Project: Parquet
> Issue Type: Improvement
> Components: parquet-mr
> Affects Versions: 1.12.0
> Reporter: Xinli Shang
> Priority: Major
> Fix For: 1.12.0
>
>
> In the last two meetings, Ryan Blue proposed to remove some unused Parquet
> modules. This is to open a task to track it.
> Here are the related meeting notes for the discussion on this.
> Remove old Parquet modules
> Hive modules - sounds good
> Scooge - Julien will reach out to twitter
> Tools - undecided - Cloudera may still use the parquet-tools according to
> Gabor.
> Cascading - undecided
> We can change the module as deprecated as description.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
