[
https://issues.apache.org/jira/browse/FLINK-20436?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17242856#comment-17242856
]
godfrey he edited comment on FLINK-20436 at 12/18/20, 8:34 AM:
---------------------------------------------------------------
Fixed in 1.13.0: deb9e6e20ff605dd4b4a78fa7e418592746719e0
was (Author: godfreyhe):
Fixed in 1.13: deb9e6e20ff605dd4b4a78fa7e418592746719e0
> Simplify type parameter of ExecNode
> -----------------------------------
>
> Key: FLINK-20436
> URL: https://issues.apache.org/jira/browse/FLINK-20436
> 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, {{ExecNode#translateToPlan}} takes {{BatchPlanner}} or
> {{StreamPlanner}} as a parameter, so {{ExecNode}} has a type parameter {{E <:
> Planner}}, which indicates the node is a batch node or a streaming node.
> While in the future, a plan may contain both batch nodes and stream node. The
> type parameter can be removed, the implementation base class can cast the
> planner to expected planner.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
