slinkydeveloper opened a new pull request #18065:
URL: https://github.com/apache/flink/pull/18065
## What is the purpose of the change
Introduce `flink-table-api-bridge-common`. This is required to load the
`DataStreamQueryOperation` and `ExternalQueryOperation` without loading
scala-api-bridge in planner. This also allowed us to deduplicate
`JavaDataStreamQueryOperation` and `ScalaDataStreamQueryOperation`, which are
essentially the same class.
Together with it, I also introduced `StreamExecutorFactory` to remove the
reflections based hack to use the
`ExecutorFactory#create(StreamExecutionEnvironment)` method.
## Brief change log
* Introduce `flink-table-api-bridge-common`
* Deduplicate `DataStreamQueryOperation` and `ExternalQueryOperation` and
move to `flink-table-api-bridge-common`
* Introduced `StreamExecutorFactory` and changed call sites which were using
reflections
## Verifying this change
This change is a trivial rework / code cleanup. This is widely covered by
e2e tests, examples and planner tests which are using both
flink-table-api-scala-bridge and flink-table-api-java-bridge
## Does this pull request potentially affect one of the following parts:
- Dependencies (does it add or upgrade a dependency): no
- The public API, i.e., is any changed class annotated with
`@Public(Evolving)`: no
- The serializers: no
- The runtime per-record code paths (performance sensitive): no
- Anything that affects deployment or recovery: JobManager (and its
components), Checkpointing, Kubernetes/Yarn, ZooKeeper: no
- The S3 file system connector: no
## Documentation
- Does this pull request introduce a new feature? no
- If yes, how is the feature documented? not applicable
--
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]
