alamb commented on issue #14296:
URL: https://github.com/apache/datafusion/issues/14296#issuecomment-2614324472

   > We have type coercion in logical plan now, consider the case where we want 
to separate logical types and physical types, should we add another type 
coercion layer in physical optimizer?
   
   I think it would make more sense to insist that the types line up exactly 
(have been resolved) in the Physical plans / physical types. But I haven't 
really thought through the implications of type coercion with a logical / 
physical type split


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

Reply via email to