[
https://issues.apache.org/jira/browse/FLINK-21549?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
godfrey he updated FLINK-21549:
-------------------------------
Description:
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.
We can do the similar things for the Sink.
was:Currently, Flink supports different kinds of push-down: projection,
filter, watermark, limit, partition, 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.
> Support json serialization/deserialization for the abilities of Source and
> Sink
> -------------------------------------------------------------------------------
>
> Key: FLINK-21549
> URL: https://issues.apache.org/jira/browse/FLINK-21549
> Project: Flink
> Issue Type: Sub-task
> Components: Table SQL / Planner
> Reporter: godfrey he
> Assignee: godfrey he
> Priority: Major
> Fix For: 1.13.0
>
>
> 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.
> We can do the similar things for the Sink.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
