Phoenix500526 opened a new pull request, #23710:
URL: https://github.com/apache/datafusion/pull/23710
## 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 #23500.
## 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.
-->
Physical plan serialization currently relies on centralized type
dispatch in `datafusion-proto`. This separates serialization from the
plans that own the relevant state and requires every built-in plan to
be handled specially.
Moving serialization into each plan keeps that logic with its owner and
allows the central dispatch chain to be removed incrementally.
`CoalesceBatchesExec` is deprecated but remains a supported public type.
Migrating its existing serialization keeps the dispatch model
consistent without extending its lifetime or changing its behavior.
## 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.
-->
- Add per-plan protobuf encoding and decoding for:
- `CoalesceBatchesExec`
- `CoalescePartitionsExec`
- `CooperativeExec`
- `BufferExec`
- Route decoding through each plan's `try_from_proto` implementation.
- Remove the corresponding centralized encoding branches.
- Retain the old public conversion helpers as deprecated compatibility
APIs.
- Preserve the existing protobuf wire representation.
- Add roundtrip coverage for `CooperativeExec` and `BufferExec`.
## 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.
-->
There are no runtime behavior or protobuf wire-format changes.
The old `PhysicalPlanNodeExt` conversion helpers remain available but
are deprecated in favor of the per-plan serialization hooks.
--
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]
