andygrove opened a new issue, #3221: URL: https://github.com/apache/arrow-datafusion/issues/3221
**Is your feature request related to a problem or challenge? Please describe what you are trying to do.** We currently do a lot of type coercion in the physical planning phase. I would like the ability to have type coercion and validation happen in the logical plan. This would benefit projects such as Dask SQL that are using the SQL query planner. **Describe the solution you'd like** Add a new `TypeCoercion` rule that adds explicit CASTs where appropriate. **Describe alternatives you've considered** None **Additional context** None -- 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]
