You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@flink.apache.org by "godfrey he (Jira)" <ji...@apache.org> on 2021/03/02 02:29:00 UTC

[jira] [Assigned] (FLINK-21549) Support json serialization/deserialization for the push-down results

     [ https://issues.apache.org/jira/browse/FLINK-21549?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

godfrey he reassigned FLINK-21549:
----------------------------------

    Assignee: godfrey he

> Support json serialization/deserialization for the push-down results
> --------------------------------------------------------------------
>
>                 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 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.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)