jayzhan211 commented on issue #14987: URL: https://github.com/apache/datafusion/issues/14987#issuecomment-2696573839
What do you mean "simplify", is it `SimplifyExpressions` or other logic. If it is `SimplifyExpressions`, then you have logical plan optimization involved, if not and you go directly to `create_physical_expr` then I think this is the issue similar to Comet where they don't have coerced types for `create_physical_expr` and they need to done the coercion part themselves. Alternative idea is that we need to introduce another `create_physical_expr_from_non_resolved` that allows inputs that are "not resolved" (so we need to do coercion or type related casting things) and keep current `create_physical_expr` for inputs that are "resolved" and used for DataFusion or other projects that has DataFusion logical plan optimization. -- 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: github-unsubscr...@datafusion.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: github-unsubscr...@datafusion.apache.org For additional commands, e-mail: github-h...@datafusion.apache.org
