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 2020/12/18 12:38:00 UTC

[jira] [Closed] (FLINK-20668) Introduce translateToExecNode method for FlinkPhysicalRel

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

godfrey he closed FLINK-20668.
------------------------------
    Resolution: Done

Fixed in 1.13.0: aab59c2084a4770a3bf75b14ad8612c08ae8fee5

> Introduce translateToExecNode method for FlinkPhysicalRel
> ---------------------------------------------------------
>
>                 Key: FLINK-20668
>                 URL: https://issues.apache.org/jira/browse/FLINK-20668
>             Project: Flink
>          Issue Type: Sub-task
>          Components: Table SQL / Planner
>            Reporter: godfrey he
>            Assignee: godfrey he
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 1.13.0
>
>
> Currently, we introduce ExecGraphGenerator to translate a graph of FlinkPhysicalRel to a ExecNode graph. While as more and more ExecNode supported, ExecGraphGenerator is hard to maintain. So we introduce FlinkPhysicalRel#translateToExecNode to create specific ExecNode in each physical RelNode, and ExecGraphGenerator is used to build the whole graph based on the translated ExecNode, including connecting the input/output nodes, handling the rel visitor, handle some special nodes (such as, Exchange), etc.



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