djanand opened a new pull request, #1919:
URL: https://github.com/apache/datafusion-ballista/pull/1919
# Which issue does this PR close?
<!--
We generally require a GitHub issue to be filed for all bug fixes and
enhancements and this helps us generate change logs for our releases. You can
link an issue to this PR using the GitHub syntax. For example `Closes #123`
indicates that this PR will close issue #123.
-->
Closes #.
# Rationale for this change
<!--
Why are you proposing this change? If this is already explained clearly in
the issue then this section is not needed.
Explaining clearly why changes are proposed helps reviewers understand your
changes and offer better suggestions for fixes.
-->
#1906 upgraded the main workspace to DataFusion 54, but the `python/`
sub-project (a separate Cargo workspace that path-depends on the ballista
crates) was left pinned to DataFusion 53. As a result, `python/` now mixes two
DataFusion majors: `pyballista` compiles the ballista path-deps against
datafusion 54 while its own `datafusion` dependency resolves to 53, which fails
to build:
```
the trait bound datafusion::prelude::SessionConfig:
ballista::extension::SessionConfigExt is not satisfied
= note: there are multiple different versions of crate
datafusion_execution in the dependency graph
```
This PR brings `python/` up to DataFusion 54 so the python build is
consistent again.
# What changes are included in this PR?
<!--
There is no need to duplicate the description in the issue here but it is
sometimes worth providing a summary of the individual changes in this PR.
-->
Bump the `python/` sub-project from DataFusion 53 to 54, keeping both
ecosystems in lockstep:
- `python/Cargo.toml` — `datafusion`, `datafusion-proto`,
`datafusion-python` → `54`
- `python/pyproject.toml` — `datafusion==54`
- `python/Cargo.lock` — regenerated (now resolves a single datafusion major,
`54`)
- `python/uv.lock` — regenerated (`datafusion` python package → `54`)
No source changes were required
Verified locally: `cargo check`, `maturin develop`, and `pytest` (`73
passed, 1 skipped`) all succeed against DataFusion 54.
# Are there any user-facing changes?
<!--
If there are user-facing changes then we may require documentation to be
updated before approving the PR.
-->
The `ballista` Python package now builds against and requires DataFusion 54
(`datafusion==54`). No API changes to the package itself.
<!--
If there are any breaking changes to public APIs, please add the `api
change` label.
-->
No breaking changes to public Rust APIs.
--
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]
