mzabaluev commented on code in PR #26589:
URL: https://github.com/apache/datafusion/pull/26589#discussion_r4590626065


##########
datafusion/physical-expr/src/expressions/case.rs:
##########
@@ -211,10 +302,79 @@ impl CaseBody {
 
         Ok(ProjectedCaseBody {
             projection,
+            precomputed: precomputed.into_iter().collect(),
             body: projected_body,
             supports_projection,
         })
     }
+
+    /// Iterates over all the top-level expressions of this case body.
+    fn exprs(&self) -> impl Iterator<Item = &Arc<dyn PhysicalExpr>> {
+        self.expr
+            .iter()
+            .chain(self.when_then_expr.iter().flat_map(|(w, t)| [w, t]))
+            .chain(self.else_expr.iter())
+    }
+}
+
+/// Returns true if `expr` is a cheap, non-volatile expression over columns 
and literals,
+/// such as a struct field access, that can be evaluated for the whole input 
batch ahead of
+/// the `CASE` branches.
+///
+/// Expressions with [`ExpressionPlacement::MoveTowardsLeafNodes`] placement 
may be pushed

Review Comment:
   Good catch! The issue is not limited to this PR, though, there are existing 
optimizations on `main` that rely on `MoveTowardsLeafNodes` designating the 
expression as safe to evaluate on rows where it would not be evaluated by an 
unoptimized plan. I have filed this as #27487.



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