Phillip Cloud created ARROW-2934:
Summary: [Packaging] Add checksums creation to sign subcommand
Key: ARROW-2934
URL: https://issues.apache.org/jira/browse/ARROW-2934
Project: Apache Arrow
Is
Phillip Cloud created ARROW-2935:
Summary: [Packaging] Add verify_binary_artifacts function to
verify-release-candidate.sh
Key: ARROW-2935
URL: https://issues.apache.org/jira/browse/ARROW-2935
Project
Wes McKinney created ARROW-2936:
---
Summary: [Python] Implement Table.cast for casting from one schema
to another (if possible)
Key: ARROW-2936
URL: https://issues.apache.org/jira/browse/ARROW-2936
Projec
I dislike the current build system complications as well.
However, in my opinion, combining the code bases will severely impact the
progress of the parquet-cpp project and implicitly the progress of the
entire parquet project.
Combining would have made much more sense if parquet-cpp is a mature
pr
Could this work as each module gets configured as sub-git repots. Top level
build tool go into each sub-repo, pick the correct release version to test.
Tests in Python is dependent on cpp sub-repo to ensure the API still pass.
This should be the best of both worlds, if sub-repo are supposed option
hi Deepak,
responses inline
On Sun, Jul 29, 2018 at 10:44 PM, Deepak Majeti wrote:
> I dislike the current build system complications as well.
>
> However, in my opinion, combining the code bases will severely impact the
> progress of the parquet-cpp project and implicitly the progress of the
>
hi Donald,
This would make things worse, not better. Code changes routinely
involve changes to the build system, and so you could be talking about
having to making changes to 2 or 3 git repositories as the result of a
single new feature or bug fix. There isn't really a cross-repo CI
solution avail
I do not claim to have insight into parquet-cpp development. However, from
our experience developing Ray, I can say that the monorepo approach (for
Ray) has improved things a lot. Before we tried various schemes to split
the project into multiple repos, but the build system and test
infrastructure
