andygrove opened a new pull request, #2738:
URL: https://github.com/apache/datafusion-comet/pull/2738
## 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
## 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.
-->
- Finish refactoring operator serde to use new framework, similar to what we
have done for expressions
- Fix issues with enabling/disabling operators via configs
- Disable `WindowExec` by default via config
- Fix inconsistencies in CometSink fallback handling
## 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.
-->
Created new classes containing operator serde logic. There are no functional
changes to this code. It has just been moved out of `QueryPlanSerde`. This was
entirely manual effort - no AI was used.
Note that `operator2proto` still has the same match statement and simply
delegates to these classes. I am working on using a map lookup approach in
https://github.com/apache/datafusion-comet/pull/2736 but it has exposed some
issues that will take time to figure out.
- CometAggregate
- CometExpand
- CometFilter
- CometGlobalLimit
- CometHashJoin
- CometLocalLimit
- CometNativeScan
- CometSortMergeJoin
- CometWindow
Moved some traits out of `QueryPlanSerde` into their own files. No code
changes made.
- CometOperatorSerde
- CometExpressionSerde
- CometAggregateExpressionSerde
- CometScalarFunction
## 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)?
-->
--
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]
