andygrove opened a new pull request, #7250: URL: https://github.com/apache/datafusion-comet/pull/7250
## Which issue does this PR close? N/A. Related: #6410 and #7249. ## Rationale for this change Comet tracks the next DataFusion major version on a long-lived branch that builds against DataFusion `main`, so that breaks and regressions surface while there is still time to fix them upstream. The DataFusion 56 upgrade does this on the `datafusion-56` branch (#7249, which replaces #6404 from a fork). The contributor guide doesn't describe the process, so the next upgrade would have to reconstruct it from old pull requests. ## What changes are included in this PR? A new contributor guide page, `upgrading_datafusion.md`, linked under "Project Mechanics". It covers: - the `datafusion-N` branch in this repository, its draft pull request and the EPIC that tracks regressions - pinning every DataFusion crate to one `main` revision, moving Arrow, Parquet and object_store with it, and pinning dependencies like iceberg-rust that must share the Arrow version - fixing the build from DataFusion's upgrade guide, handling deprecations without a replacement, and checking DataFusion's behavior changes against Comet - the CI labels to add, since the default checks don't run Spark's SQL tests, the Iceberg suites or the Delta contrib suites - tracing each regression to the project that owns it, fixing it there, and ignoring and documenting a test when the fix won't land in time - switching to the released crates and merging once DataFusion N.0.0 ships ## How are these changes tested? Documentation only. `prettier --check` passes on both changed files. -- 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]
