Re: [I] Support to_timestamp with 2 arguments (timestamp format) [arrow-datafusion]

["Omega359 (via GitHub)" <gi...@apache.org>]

Omega359 commented on issue #5398:
URL: https://github.com/apache/arrow-datafusion/issues/5398#issuecomment-1890785066

   Question on implementation detail while implementing this: should this throw an Err if the timestamp cannot be parsed given either the default behaviour or if the provided formats are provided? Current behaviour seems to be be to throw an Err which mirrors postgresql behaviour, whereas with spark for example the behaviour is to return null for any unparseable string.
   
   I'm asking because with date/timestamp string parsing you are often not dealing with machine generated data but rather human generated and there are only so many formats that can be tried before you must just set the data to null and move on. Not having that ability could be a hindrance for some use cases.
   
   A thought I did have would be to change the behaviour via flag that would be documented as part of the api and user guide. 


-- 
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-unsubscribe@arrow.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org