> 4. Verified the signatures using the commands below (not sure if the
WARNING is something we should fix)
I believe the warning is caused by my key not being signed by others
in the network, I will get that fixed.
Thank you Andy for the quick fix, I will send a voting thread for rc2
later tonigh
Here is a PR to resolve this
https://github.com/apache/arrow-datafusion/pull/852
On Tue, Aug 10, 2021 at 4:24 PM Andy Grove wrote:
> Hi QP,
>
> This looks great overall but I did run into one issue. The Ballista crates
> have relative paths for dependencies rather than depending on versioned
>
Hi QP,
This looks great overall but I did run into one issue. The Ballista crates
have relative paths for dependencies rather than depending on versioned
crates, so we would not be able to publish them to crates.io
*$ find ballista -name Cargo.toml -exec grep -H "path" {} \;*
ballista/rust/schedu
+1 (binding)
I did the following
1. downloaded the tarball and ran `cargo test --all` on mac OS (x86_64)
2. Verified the versions in Cargo.toml files for datafusion, ballista and
python crates (some of the unpublished crates like datafusion-cli still say
4.0.0-SNAPSHOT)
3. Verified the shasum usin
Hi,
I would like to propose a release of Apache Arrow Datafusion Implementation,
version 5.0.0.
This release candidate is based on commit:
96658eb100436c47601ed10095d74299d2229020 [1]
The proposed release tarball and signatures are hosted at [2].
The changelog is located at [3].
Please download,
