comphead commented on issue #5259: URL: https://github.com/apache/arrow-datafusion/issues/5259#issuecomment-1428974364
@ozankabak Its probably point of long disputes what is better: failfast or return null/nan etc. I'm still thinking we should stick to PG behavior, as it is consistent and expectable from users migrating their queries. From personal point of view it seems failfast is better solution anyway as it doesn't silently corrupt the data and give the user responsibility how to deal with bad data on his side. Math function has to be simple and support only supportable data for given function. Other day old spark versions turned the value into null if it cannot be casted to timestamp and this was sooooo frustrating, that spark went away and now the `to_timestamp` function fails fast. -- 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]
