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 08:36:00 UTC
[jira] [Comment Edited] (FLINK-20490) Don't share inputs between
FlinkPhysicalRel and ExecNode
[ https://issues.apache.org/jira/browse/FLINK-20490?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17245849#comment-17245849 ]
godfrey he edited comment on FLINK-20490 at 12/18/20, 8:35 AM:
---------------------------------------------------------------
Fixed in 1.13.0: 314b4d0442da391ef7e56c6cea817eccf43bf2a3
was (Author: godfreyhe):
master: 314b4d0442da391ef7e56c6cea817eccf43bf2a3
> Don't share inputs between FlinkPhysicalRel and ExecNode
> --------------------------------------------------------
>
> Key: FLINK-20490
> URL: https://issues.apache.org/jira/browse/FLINK-20490
> 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, all execution nodes extend both from {{RelNode}} and {{ExecNode}}, and they share same input instances which is stored in the {{RelNode}} instance. {{ExecNode#getInputNodes}} just returns the casted {{RelNode}} inputs, code likes:
> {code:java}
> getInputs.map(_.asInstanceOf[ExecNode[_]])
> {code}
> This issue aim to let {{ExecNode}} have its own input instances. It is prepared for the implementation separation between {{RelNode}} and {{ExecNode}}.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)