Skip to content

refactor(proto): remove legacy scan field - #23445

Merged
alamb merged 2 commits into
apache:mainfrom
Phoenix500526:remove/partitioned_by_file_group-compatibility
Jul 26, 2026
Merged

refactor(proto): remove legacy scan field#23445
alamb merged 2 commits into
apache:mainfrom
Phoenix500526:remove/partitioned_by_file_group-compatibility

Conversation

@Phoenix500526

Copy link
Copy Markdown
Contributor

Which issue does this PR close?

  • Closes #N/A.

Rationale for this change

Since DataFusion doesn't typically guartantee wire format compatibility, I remove the backward compatiblity shim that introduced in PR #23189

FYI: #23189 (comment)

What changes are included in this PR?

DataFusion does not guarantee serialized plans across versions. Keeping partitioned_by_file_group therefore leaves a dead schema field and decoder path after output_partitioning became the source of truth. Reserve the old field number and name to prevent future reuse.

Are these changes tested?

Yes

Are there any user-facing changes?

Yes

DataFusion does not guarantee serialized plans across versions. Keeping
`partitioned_by_file_group` therefore leaves a dead schema field and
decoder path after `output_partitioning` became the source of truth.
Reserve the old field number and name to prevent future reuse.
Signed-off-by: Jiawei Zhao <Phoenix500526@163.com>
@github-actionsgithub-actionsBot added documentation Improvements or additions to documentation proto Related to proto crate labels Jul 10, 2026
@github-actions

github-actionsBot commented Jul 10, 2026

Copy link
Copy Markdown

Thank you for opening this pull request!

Reviewer note: cargo-semver-checks reported the current version number is not SemVer-compatible with the changes in this pull request (compared against the base branch).

Details
 Cloning apache/main
Building datafusion-proto v54.1.0 (current)
Built [ 59.664s] (current)
Parsing datafusion-proto v54.1.0 (current)
Parsed [ 0.019s] (current)
Building datafusion-proto v54.1.0 (baseline)
Built [ 59.083s] (baseline)
Parsing datafusion-proto v54.1.0 (baseline)
Parsed [ 0.020s] (baseline)
Checking datafusion-proto v54.1.0 -> v54.1.0 (no change; assume patch)
Checked [ 0.259s] 223 checks: 223 pass, 30 skip
Summary no semver update required
Finished [ 120.371s] datafusion-proto
Building datafusion-proto-models v54.1.0 (current)
Built [ 24.590s] (current)
Parsing datafusion-proto-models v54.1.0 (current)
Parsed [ 0.129s] (current)
Building datafusion-proto-models v54.1.0 (baseline)
Built [ 24.358s] (baseline)
Parsing datafusion-proto-models v54.1.0 (baseline)
Parsed [ 0.130s] (baseline)
Checking datafusion-proto-models v54.1.0 -> v54.1.0 (no change; assume patch)
Checked [ 1.751s] 223 checks: 221 pass, 2 fail, 0 warn, 30 skip
--- failure inherent_method_missing: pub method removed or renamed ---
Description:
A publicly-visible method or associated fn is no longer available under its prior name. It may have been renamed or removed entirely.
ref: https://doc.rust-lang.org/cargo/reference/semver.html#item-remove
impl: https://github.com/obi1kenobi/cargo-semver-checks/tree/v0.49.0/src/lints/inherent_method_missing.ron
Failed in:
FileScanExecConf::partitioned_by_file_group, previously in file /home/runner/work/datafusion/datafusion/target/semver-checks/git-apache_main/aaddf2eed7ce0cd70ec49304db33795fd8ddd9b1/datafusion/proto-models/src/generated/prost.rs:1854
FileScanExecConf::partitioned_by_file_group, previously in file /home/runner/work/datafusion/datafusion/target/semver-checks/git-apache_main/aaddf2eed7ce0cd70ec49304db33795fd8ddd9b1/datafusion/proto-models/src/generated/prost.rs:1854
--- failure struct_pub_field_missing: pub struct's pub field removed or renamed ---
Description:
A publicly-visible struct has at least one public field that is no longer available under its prior name. It may have been renamed or removed entirely.
ref: https://doc.rust-lang.org/cargo/reference/semver.html#item-remove
impl: https://github.com/obi1kenobi/cargo-semver-checks/tree/v0.49.0/src/lints/struct_pub_field_missing.ron
Failed in:
field partitioned_by_file_group of struct FileScanExecConf, previously in file /home/runner/work/datafusion/datafusion/target/semver-checks/git-apache_main/aaddf2eed7ce0cd70ec49304db33795fd8ddd9b1/datafusion/proto-models/src/generated/prost.rs:1879
field partitioned_by_file_group of struct FileScanExecConf, previously in file /home/runner/work/datafusion/datafusion/target/semver-checks/git-apache_main/aaddf2eed7ce0cd70ec49304db33795fd8ddd9b1/datafusion/proto-models/src/generated/prost.rs:1879
Summary semver requires new major version: 2 major and 0 minor checks failed
Finished [ 52.026s] datafusion-proto-models

@github-actionsgithub-actionsBot added the auto detected api change Auto detected API change label Jul 10, 2026
@Phoenix500526

Copy link
Copy Markdown
ContributorAuthor

Hi @alamb , sorry to ping. Could you take a look at this PR when you have time?

This removes the legacy scan field from the proto as you mentioned in
#23189 (comment), and I would appreciate any guidance if you think the direction should change.

Thanks.

@alambalamb left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you for the followup @Phoenix500526

@alamb
alamb enabled auto-merge July 26, 2026 17:48
@alamb
alamb added this pull request to the merge queueJul 26, 2026
@codecov-commenter

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 80.65%. Comparing base (88365dd) to head (fee179f).
⚠️ Report is 1 commits behind head on main.

Additional details and impacted files
@@ Coverage Diff @@## main #23445 +/- ##
==========================================
- Coverage 80.65% 80.65% -0.01% 
==========================================
Files 1093 1093 Lines 371619 371596 -23 Branches 371619 371596 -23 ==========================================
- Hits 299730 299705 -25 
Misses 53993 53993 - Partials 17896 17898 +2 

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

Merged via the queue into apache:main with commit bb670fbJul 26, 2026
38 checks passed
@Phoenix500526
Phoenix500526 deleted the remove/partitioned_by_file_group-compatibility branch July 31, 2026 06:14
kosiew pushed a commit to kosiew/datafusion that referenced this pull request Aug 12, 2026
## 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
`Closesapache#123` indicates that this PR will close issue apache#123.
-->
- Closes #N/A.
## 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.
-->
Since DataFusion doesn't typically guartantee wire format compatibility,
I remove the backward compatiblity shim that introduced in PR apache#23189
FYI:
apache#23189 (comment)
## 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.
-->
DataFusion does not guarantee serialized plans across versions. Keeping
`partitioned_by_file_group` therefore leaves a dead schema field and
decoder path after `output_partitioning` became the source of truth.
Reserve the old field number and name to prevent future reuse.
## 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)?
-->
Yes
## Are there any user-facing changes?
<!--
If there are user-facing changes then we may require documentation to be
updated before approving the PR.
-->
<!--
If there are any breaking changes to public APIs, please add the `api
change` label.
-->
Yes
Signed-off-by: Jiawei Zhao <Phoenix500526@163.com>
Co-authored-by: Andrew Lamb <andrew@nerdnetworks.org>
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

auto detected api changeAuto detected API changedocumentationImprovements or additions to documentationprotoRelated to proto crate

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants

@Phoenix500526@codecov-commenter@alamb