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/01/29 01:39:00 UTC

[jira] [Closed] (FLINK-21105) Rename ExecEdge to InputProperty

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

godfrey he closed FLINK-21105.
------------------------------
    Resolution: Fixed

Fixed in 1.13.0: f083c672f4d3b96c8defb52f88247c548077181c

> Rename ExecEdge to InputProperty
> --------------------------------
>
>                 Key: FLINK-21105
>                 URL: https://issues.apache.org/jira/browse/FLINK-21105
>             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, the ExecEdge represents the properties for the input of an operator, the properties include
> 1. required data distribute for an input (the input corresponds to the [Input|https://github.com/apache/flink/blob/master/flink-streaming-java/src/main/java/org/apache/flink/streaming/api/operators/Input.java])
> 2. DamBehavior which describes the behaviors how an in record may trigger the output of the target operator.
> 3. the priority of this input read by the target operator
> So ExecEdge should be rename to InputProperty, and we will re-introduce ExecEdge which describes how to connect two ExecNodes in [FLINK-21150|https://issues.apache.org/jira/browse/FLINK-21150], and how to shuffle the data between two ExecNodes. Its role should be similar to StreamEdge.



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