[ https://issues.apache.org/jira/browse/ARROW-7830?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17055049#comment-17055049 ]
H. Vetinari edited comment on ARROW-7830 at 3/9/20, 3:08 PM: ------------------------------------------------------------- What does the parquet-version used here (1.5.1) stand for, actually? Upstream parquet [never had|https://github.com/apache/parquet-mr/releases?after=parquet-1.6.0rc1] a 1.5.1 release, and if it had, it would be 5-6 years old. I mean, I get that it's set [here|https://github.com/apache/arrow/tree/master/cpp/src/parquet], but the relation to arrow and/or parquet versions (or what 1.0.0 meant for that number, for that matter) is not apparent to me. was (Author: h-vetinari): What does the parquet-version used here (1.5.1) stand for, actually? Upstream parquet [never had|https://github.com/apache/parquet-mr/releases?after=parquet-1.6.0rc1] a 1.5.1 release, and if it had, it would be 5-6 years old. > [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)