[ https://issues.apache.org/jira/browse/ARROW-7830?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17055974#comment-17055974 ]
Wes McKinney commented on ARROW-7830: ------------------------------------- > 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)? This wasn't what was agreed on the Parquet mailing list when we voted to create the monorepo setup. We can always revisit that discussion. > [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)