twalthr commented on a change in pull request #17652:
URL: https://github.com/apache/flink/pull/17652#discussion_r741769770



##########
File path: 
flink-table/flink-table-planner/src/test/resources/org/apache/flink/table/planner/plan/nodes/exec/stream/TableSourceJsonPlanTest_jsonplan/testPartitionPushDown.out
##########
@@ -64,7 +61,7 @@
         "b" : "INT"
       } ]
     },
-    "description" : "TableSourceScan(table=[[default_catalog, 
default_database, PartitionTable, filter=[], partitions=[{p=A}], project=[a, 
b], metadata=[]]], fields=[a, b])",
+    "description" : "TableSourceScan(table=[[default_catalog, 
default_database, PartitionTable, partitions=[{p=A}], project=[a, b], 
metadata=[]]], fields=[a, b])",

Review comment:
       > specs will be print each by the order in which they added to the table 
source
   
   My question if the print order is consistent everywhere for the specs. But I 
don't think we need more tests for now. Thanks.

##########
File path: 
flink-table/flink-table-planner/src/test/resources/org/apache/flink/table/planner/plan/nodes/exec/stream/TableSourceJsonPlanTest_jsonplan/testPartitionPushDown.out
##########
@@ -64,7 +61,7 @@
         "b" : "INT"
       } ]
     },
-    "description" : "TableSourceScan(table=[[default_catalog, 
default_database, PartitionTable, filter=[], partitions=[{p=A}], project=[a, 
b], metadata=[]]], fields=[a, b])",
+    "description" : "TableSourceScan(table=[[default_catalog, 
default_database, PartitionTable, partitions=[{p=A}], project=[a, b], 
metadata=[]]], fields=[a, b])",

Review comment:
       > specs will be print each by the order in which they added to the table 
source
   
   My question was rather if the print order is consistent everywhere for the 
specs. But I don't think we need more tests for now. Thanks.




-- 
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]


Reply via email to