godfreyhe opened a new pull request #14478:
URL: https://github.com/apache/flink/pull/14478
## What is the purpose of the change
*Separate the implementation of stream group aggregate nodes*
## Brief change log
- *Introduce StreamPhysicalGroupAggregate, and make
StreamExecGroupAggregate only extended from ExecNode*
- *Introduce StreamPhysicalPythonGroupAggregate, and make
StreamExecPythonGroupAggregate only extended from ExecNode*
- *Introduce StreamPhysicalLocalGroupAggregate, and make
StreamExecLocalGroupAggregate only extended from ExecNode*
- *Introduce StreamPhysicalGlobalGroupAggregate, and make
StreamExecGlobalGroupAggregate only extended from ExecNode*
- *Introduce StreamPhysicalIncrementalGroupAggregate, and make
StreamExecIncrementalGroupAggregate only extended from ExecNode*
- *Introduce StreamPhysicalGroupTableAggregate, and make
StreamExecGroupTableAggregate only extended from ExecNode*
- *Introduce StreamPhysicalPythonGroupTableAggregate, and make
StreamExecPythonGroupTableAggregate only extended from ExecNode*
## Verifying this change
This change is a refactoring rework covered by existing tests.
## Does this pull request potentially affect one of the following parts:
- Dependencies (does it add or upgrade a dependency): (yes / **no**)
- The public API, i.e., is any changed class annotated with
`@Public(Evolving)`: (yes / **no**)
- The serializers: (yes / **no** / don't know)
- The runtime per-record code paths (performance sensitive): (yes / **no**
/ don't know)
- Anything that affects deployment or recovery: JobManager (and its
components), Checkpointing, Kubernetes/Yarn/Mesos, ZooKeeper: (yes / **no** /
don't know)
- The S3 file system connector: (yes / **no** / don't know)
## Documentation
- Does this pull request introduce a new feature? (yes / **no**)
- If yes, how is the feature documented? (not applicable / docs / JavaDocs
/ **not documented**)
----------------------------------------------------------------
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.
For queries about this service, please contact Infrastructure at:
[email protected]
