You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@parquet.apache.org by "Wes McKinney (JIRA)" <ji...@apache.org> on 2016/01/05 18:14:39 UTC
[jira] [Commented] (PARQUET-416) Add option for using portable
external toolchain, C++11, cpplint cleanup, package target and header
installation
[ https://issues.apache.org/jira/browse/PARQUET-416?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15083382#comment-15083382 ]
Wes McKinney commented on PARQUET-416:
--------------------------------------
Related; PARQUET-267. I will incorporate those changes (and other feedback from this PR) and report back.
> Add option for using portable external toolchain, C++11, cpplint cleanup, package target and header installation
> ----------------------------------------------------------------------------------------------------------------
>
> Key: PARQUET-416
> URL: https://issues.apache.org/jira/browse/PARQUET-416
> Project: Parquet
> Issue Type: Improvement
> Components: parquet-cpp
> Reporter: Wes McKinney
>
> I'm planning to work on building out parquet-cpp with columnar data structures (see Arrow proposal) for materialized in-memory data and feature complete reader/writers so that native-code consumers like Python can finally read and write Parquet files at native speeds. It would be great to have all this officially a part of Apache Parquet.
> To that end, I have removed the thirdparty libraries and added optional support for the open source external C++ toolchain available at github.com/cloudera/native-toolchain.
> This also adds minimal support to be able to install the resulting libparquet.so and its various header files to support minimally viable development on downstream C++ and Python projects that will need to depend on this.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)