comphead opened a new pull request, #5865:
URL: https://github.com/apache/datafusion-comet/pull/5865
## 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.
-->
N/A. Routine dependency bump, no issue filed.
## 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.
-->
Pick up the bugfixes in DataFusion 55.1.0. It is a patch release over 55.0.0
(10 commits, all fixes, no API changes). The ones most relevant to Comet:
- `fix: make UnnestExec respect datafusion.execution.batch_size`
([#24529](https://github.com/apache/datafusion/pull/24529))
- `fix: apply struct field filters when the file schema needs adaptation`
([#24530](https://github.com/apache/datafusion/pull/24530))
- `fix: adapt input batches with stricter nested nullability to planned
schema in aggregation`
([#24699](https://github.com/apache/datafusion/pull/24699))
- `Fix panic on RightMark hash joins when propagating ordering`
([#24759](https://github.com/apache/datafusion/pull/24759))
- `fix(common): support empty struct in ScalarValue::compact and
new_default` ([#24876](https://github.com/apache/datafusion/pull/24876))
- `Align metadata propagation through Physical and Logical casts`
([#24875](https://github.com/apache/datafusion/pull/24875))
- `fix: preserve projection metadata during optimization`
([#24992](https://github.com/apache/datafusion/pull/24992))
Full changelog:
https://github.com/apache/datafusion/blob/55.1.0/dev/changelog/55.1.0.md
## 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.
-->
- `native/Cargo.toml`: `datafusion`, `datafusion-datasource`,
`datafusion-physical-expr-adapter`
and `datafusion-spark` bumped `55.0.0` -> `55.1.0`.
- `native/core/Cargo.toml`: `datafusion-functions-nested` bumped `55.0.0` ->
`55.1.0`.
- `contrib/delta/native/Cargo.toml`: `datafusion` bumped `55.0.0` ->
`55.1.0`.
- Both lockfiles refreshed with `cargo update`.
No Comet source changes were needed. `arrow`, `parquet` and `object_store`
are
unchanged in `native/Cargo.lock` (59.3.0 / 59.3.0 / 0.13.2); the remaining
lock
churn there is patch-level bumps of transitive crates (aws-sdk-*, reqwest,
rustls, wasm-bindgen, zstd, ...).
One thing worth a reviewer's eye: `contrib/delta/native/Cargo.lock` had
drifted
out of sync with its own manifest. It still pinned `datafusion 54.0.0` (and
`arrow`/`parquet` 58.3.0) while `contrib/delta/native/Cargo.toml` already
asked
for `55.0.0`, so a `--locked` build of that crate could not have succeeded.
Regenerating it moves that crate to `datafusion 55.1.0` and `arrow`/`parquet`
59.3.0, matching what the `native/` workspace already resolves for it. That
accounts for most of the diff in that file.
## How are these changes tested?
<!--
We typically require tests for all PRs in order to:
1. Prevent the code from being accidentally broken by subsequent changes
2. Serve as another way to document the expected behavior of the code
If tests are not included in your PR, please explain why (for example, are
they covered by existing tests)?
-->
Existing CI. Locally verified on macOS/aarch64:
- `cargo check --workspace --all-targets --locked` — clean
- `cargo clippy --workspace --all-targets --locked -- -D warnings` — clean
- `cargo fmt --all -- --check` — clean
- `cargo check -p datafusion-comet --features contrib-delta --locked` — clean
- `cargo check --locked --all-targets` in `contrib/delta/native` — clean
No JVM or Spark SQL suites were run locally; relying on CI for those.
--
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]
