Dandandan commented on code in PR #21240:
URL: https://github.com/apache/datafusion/pull/21240#discussion_r3011728198


##########
datafusion/physical-plan/src/scalar_subquery.rs:
##########
@@ -237,6 +237,10 @@ impl ExecutionPlan for ScalarSubqueryExec {
         self.true_for_input_only()
     }
 
+    fn partition_statistics(&self, partition: Option<usize>) -> 
Result<Arc<Statistics>> {
+        self.input.partition_statistics(partition)

Review Comment:
   The idea is mostly that the subquery will have either unknown or high 
estimated stats, returning updated stats for a *scalar* subquery should 
generally be much more effective for planning correct join order, as it can be 
loaded in the build side.



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


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to