alamb commented on PR #14273: URL: https://github.com/apache/datafusion/pull/14273#issuecomment-2614039003
I have been thinking about this more. Is it a crazy idea if we tried to implement "user defined coercion rules" -- that way we can have whatever coercion rules are in the DataFusion core but when they inevitably are not quite what users want (as @findepi has pointed out many examples) that way users can customize them however they want I feel like with the current requirement for a single set of coercion rules, we'll always end up with conflicting requiements such as - https://github.com/apache/datafusion/pull/14223 Rather than having to go back/forth in the core and find some compromise an API would give us an escape hatch. It would also force us to design the type coercion APIs more coherently which I think would be good for the code quality in general 🤔 If you think it is an idea worth exploring I will file a ticket -- 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
