andygrove opened a new pull request, #2127:
URL: https://github.com/apache/datafusion-ballista/pull/2127
# Which issue does this PR close?
N/A
# Rationale for this change
DataFusion 54.1.0 was released, so the `branch-54` release branch should
pick it up. This also bumps the Ballista crate versions to 54.1.0 in
preparation for a 54.1.0 release.
This is the `branch-54` counterpart of #2126.
# What changes are included in this PR?
- Move `Cargo.lock` and `python/Cargo.lock` to the DataFusion 54.1.0 patch
release.
- Re-sync the vendored DataFusion proto files with
`dev/update_datafusion_proto.py`, which adds the new `null_aware` field to
`JoinNode` in `ballista/core/proto/datafusion.proto`.
- Bump the Ballista crate versions from 54.0.0 to 54.1.0 via
`dev/update_ballista_versions.py`.
- Add a comment in `Cargo.toml` explaining why the `datafusion*`
requirements stay at `54`.
The workspace requirements deliberately stay at `54` rather than pinning
`54.1.0`. The `python` workspace has its own lockfile but depends on the
ballista crates by path, so an exact requirement here drags it onto 54.1.0 too,
and `datafusion-python` 54.0.0 does not compile against 54.1.0:
```
error[E0063]: missing field `schema` in initializer of
`datafusion::logical_expr::RecursiveQuery`
--> datafusion-python-54.0.0/src/expr/recursive_query.rs:72:20
```
DataFusion 54.1.0 added a `schema` field to the public `RecursiveQuery`
struct, and there is no 54.1.0 release of `datafusion-python` yet. Keeping the
requirement at `54` lets the main workspace build against 54.1.0 while
`python/Cargo.lock` stays on 54.0.0 until `datafusion-python` catches up.
The lockfile also drops a duplicate `windows-sys` 0.53/0.60 tree that the
DataFusion 54.1.0 dependency graph no longer pulls in.
# Are there any user-facing changes?
No API changes. The Ballista crates are versioned 54.1.0 and the scheduler,
executor, CLI and benchmarks build against DataFusion 54.1.0. The Python wheel
continues to build against DataFusion 54.0.0.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
