wenlong88 commented on a change in pull request #18042: URL: https://github.com/apache/flink/pull/18042#discussion_r767460228
########## File path: flink-table/flink-table-planner/src/test/resources/org/apache/flink/table/planner/plan/nodes/exec/operator/BatchOperatorNameTest.xml ########## @@ -0,0 +1,2099 @@ +<?xml version="1.0" ?> +<!-- +Licensed to the Apache Software Foundation (ASF) under one or more +contributor license agreements. See the NOTICE file distributed with +this work for additional information regarding copyright ownership. +The ASF licenses this file to you under the Apache License, Version 2.0 +(the "License"); you may not use this file except in compliance with +the License. You may obtain a copy of the License at + +http://www.apache.org/licenses/LICENSE-2.0 + +Unless required by applicable law or agreed to in writing, software +distributed under the License is distributed on an "AS IS" BASIS, +WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. +See the License for the specific language governing permissions and +limitations under the License. +--> +<Root> + <TestCase name="testBoundedStreamScan[isNameSimplifyEnabled=false]"> + <Resource name="explain"> + <![CDATA[== Abstract Syntax Tree == +LogicalProject(f0=[$0]) ++- LogicalTableScan(table=[[default_catalog, default_database, MyTable]]) + +== Optimized Physical Plan == +BoundedStreamScan(table=[[default_catalog, default_database, MyTable]], fields=[f0]) + Review comment: yes, but verifying physical exec plan by explain is a common way in planner, and if we want to do a different way ,we need to expose some more internal interface of planner in the testing class, such as planner#executor, and planner#translateToPlan(ExecNodeGraph). so I think it is ok to keep not changed. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
