westonpace opened a new issue, #34644: URL: https://github.com/apache/arrow/issues/34644
### Describe the enhancement requested Substrait specifies a failure behavior (return null or error) for casting. However, it does not specify what exactly constitutes a failure. When we added bindings for the cast expression we assumed that Substrait wanted a safe cast. However, I have since learned that most existing engines (e.g. postgres, spark, etc.) will perform an unsafe cast by default and only consider a failure when casting is impossible (e.g. "foo" to integer). I'd like to eventually see Substrait add support for specifying more precisely what kind of casting should occur. In the meantime I think we should update the default to unsafe casting to match user expectation. ### Component(s) C++ -- 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]
