[
https://issues.apache.org/jira/browse/ARROW-7830?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17055702#comment-17055702
]
H. Vetinari commented on ARROW-7830:
------------------------------------
OK, I didn't want to come off as demanding (anything, really), just trying to
understand the situation.
I had only ever seen PARQUET-xxxx associated with parquet-mr, I had never
stumbled on the [parquet-cpp repo|https://github.com/apache/parquet-cpp].
Nevertheless, the head of that repo's README starts off as:
> *Note: Development for Apache Parquet in C++ has moved*
>
> The Apache Arrow and Parquet have merged development process and build
> systems in the Arrow repository. Please submit pull requests in
> https://github.com/apache/arrow.
So wouldn't it be a reasonable way of looking at things that the arrow-project
can now set the corresponding version number (or absorb the project completely,
for example)?
> [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)
