godfreyhe opened a new pull request #15062:
URL: https://github.com/apache/flink/pull/15062
## What is the purpose of the change
*Currently, Flink supports applying different kinds of ability to Source:
projection push down, filter push, watermark push down, limit push down,
partition push down, reading metadata. The push-down result should also be
serialized to the json plan and then we can get the correct ExecNode plan from
the json plan. To avoid modifying each connector, we can store the push-down
result into the TableSourceTable during the Calcite optimization phase, and
store the push-down result into DynamicTableSourceSpec in the ExecNode graph.
The similar thing can be done for DynamicTableSink. This pr aims to support
them.*
## Brief change log
- *Support json serialization/deserialization for the push-down result of
DynamicTableSource*
- *Support json serialization/deserialization for the push-down result of
DynamicTableSink*
## Verifying this change
This change added tests and can be verified as follows:
- *Extended DynamicTableSourceSpecSerdeTest and
DynamicTableSinkSpecSerdeTest to verify the change*
## 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]
