Uh oh!
There was an error while loading. Please reload this page.
refactor(proto): remove legacy scan field - #23445
Conversation
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>
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 |
Phoenix500526
commented
Jul 17, 2026
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 Thanks. |
alamb
left a comment
There was a problem hiding this comment.
Thank you for the followup @Phoenix500526
codecov-commenter
commented
Jul 26, 2026
Codecov Report✅ All modified and coverable lines are covered by tests. 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. 🚀 New features to boost your workflow:
|
Uh oh!
There was an error while loading. Please reload this page.
## 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>
Which issue does this PR close?
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_grouptherefore leaves a dead schema field and decoder path afteroutput_partitioningbecame 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