[
https://issues.apache.org/jira/browse/ARROW-7830?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17055223#comment-17055223
]
Wes McKinney commented on ARROW-7830:
-------------------------------------
parquet-cpp has separate release numbers from parquet-mr
The Parquet community is welcome to make parquet-cpp releases and then we can
bump the corresponding version number in the codebase. Releasing is work and if
there are no volunteers to push releases to happen then they will not happen
> [C++] Parquet library version doesn't change with releases
> ----------------------------------------------------------
>
> Key: ARROW-7830
> URL: https://issues.apache.org/jira/browse/ARROW-7830
> Project: Apache Arrow
> Issue Type: Bug
> Components: C++
> Reporter: Neal Richardson
> Priority: Major
> Labels: parquet
>
> [~jeroenooms] pointed this out to me.
> {code}
> $ pkg-config --modversion arrow
> 0.16.0
> $ pkg-config --modversion arrow-dataset
> 0.16.0
> $ pkg-config --modversion parquet
> 1.5.1-SNAPSHOT
> {code}
> I get that parquet-cpp is technically not part of Apache Arrow, but if we're
> releasing a libparquet with libarrow at our release time, wouldn't it make
> sense to at least bump the parquet version at the same time, even if the
> version numbers aren't the same?
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
