-
Notifications
You must be signed in to change notification settings - Fork 1.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Release DataFusion 21.1.0 #5744
Comments
Thanks @alamb. There is a |
I have created a release candidate here: https://lists.apache.org/thread/qw5067glfmxy4k42wty4vph7pjkgq24p |
I am now waiting for the 3 day voting period. Once that has elapsed, assuming no |
The release is approved and available: https://lists.apache.org/thread/tmfzkqnvkmccmy8w2ltpqh0sy4mgy6qq However, unfortunately I am still working on publishing it to crates.io ((I do not have permissions to https://crates.io/crates/datafusion-execution/21.0.0) Perhaps @andygrove can help here |
I have published the release to crates.io (thank you @andygrove ) Since this release only includes a dependency improvement (rather than any features) I am not planning to publish an update on homebrew. |
I have published the release to crates.io (thank you @andygrove ) Since this release only includes a dependency improvement (rather than any features) I am not planning to publish an update on homebrew. |
Thanks @alamb. I'm unforunately still seeing both Arrow 35 and arrow 34 pulled in. I may be missing something, but here's what I'm trying. Fresh Cargo.toml [package]
name = "datafusion_arrow_35"
version = "0.1.0"
edition = "2021"
[dependencies]
datafusion="21.1.0"
arrow="35.0.0" If I run
In particular:
Happy to open a new issue if that's easier than discussing here |
@jonmmease 🤔 I wonder if you can try runnning |
(note that datafusion-21 still depends on arrow-rs 34) -- only datafusion 22.0.0 upgrades to arrow-rs 36. So in other words this is expected in my mind:
|
Ah, ok. I was seeing the mixed arrow 34/35 dependencies with datafusion 21.0.0 and assumed that it was intended to depend fully on arrow 35. Thanks for the clarification. |
No problem -- we decided to skip arrow-35 due to several regressions in parsing timestamps (see #5441 (comment) for more details) Edit: I also updated the PR description to make the ('only depend on arrow 34.0.0') more explicit |
Is your feature request related to a problem or challenge?
During testing of Version 21.0.0 RC1 we discovered that it inadvertently depends both on arrow (and its subcrates) version
34.0.0
as well asarrow-array
version35.0.0
This feature was fixed in #5724 (so datafusion only depends on arrow 34.0.0)
https://lists.apache.org/thread/fnnmrn83spnb2y2l2vdw2v1hd54pfjl7
Describe the solution you'd like
I propose releasing DataFusion 21.1.0 with the fix in #5724
Describe alternatives you've considered
We could do nothing and wait for DataFusion 22.0.0 in a few weeks time.
Additional context
No response
The text was updated successfully, but these errors were encountered: