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/07 10:49:00 UTC
[jira] [Created] (FLINK-20509) Refactor verifyPlan method in
TableTestBase
godfrey he created FLINK-20509:
----------------------------------
Summary: Refactor verifyPlan method in TableTestBase
Key: FLINK-20509
URL: https://issues.apache.org/jira/browse/FLINK-20509
Project: Flink
Issue Type: Sub-task
Components: Table SQL / Planner
Reporter: godfrey he
Currently, we use {{verifyPlan}} method to verify the plan result for both {{RelNode}} plan and {{ExecNode}} plan, because their instances are the same. But once the implementation of {{RelNode}} and {{ExecNode}} are separated we can't get {{ESTIMATED_COST}} and {{CHANGELOG_MODE}} on {{ExecNode}} plan. So in order to make the methods more clear, the {{verifyPlan}} method can be separated into two methods, {{verifyRelPlan}} for verifying the {{RelNode}} plan, and {{verifyExecPlan}} for verifying the {{ExecNode}} plan.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)