[jira] [Updated] (PARQUET-416) C++11, cpplint cleanup, package target and header installation
[ https://issues.apache.org/jira/browse/PARQUET-416?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wes McKinney updated PARQUET-416: - Summary: C++11, cpplint cleanup, package target and header installation (was: Add option for using portable external toolchain, C++11, cpplint cleanup, package target and header installation) > 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)
[jira] [Updated] (PARQUET-416) C++11, cpplint cleanup, package target and header installation
[ https://issues.apache.org/jira/browse/PARQUET-416?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wes McKinney updated PARQUET-416: - External issue URL: https://github.com/apache/parquet-cpp/pull/14 (was: https://github.com/apache/parquet-cpp/pull/13) > 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)
[jira] [Updated] (PARQUET-416) C++11, cpplint cleanup, package target and header installation
[ https://issues.apache.org/jira/browse/PARQUET-416?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wes McKinney updated PARQUET-416: - Description: 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. This 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. It also builds in C++11 mode and passes Google's cpplint. was: 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. > 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. > This 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. It also > builds in C++11 mode and passes Google's cpplint. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (PARQUET-416) C++11, cpplint cleanup, package target and header installation
[ https://issues.apache.org/jira/browse/PARQUET-416?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nong Li updated PARQUET-416: Assignee: Wes McKinney > 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 >Assignee: 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. > This 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. It also > builds in C++11 mode and passes Google's cpplint. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (PARQUET-416) C++11, cpplint cleanup, package target and header installation
[ https://issues.apache.org/jira/browse/PARQUET-416?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nong Li updated PARQUET-416: Fix Version/s: (was: format-2.4.0) > 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 >Assignee: 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. > This 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. It also > builds in C++11 mode and passes Google's cpplint. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
