westonpace commented on issue #686: URL: https://github.com/apache/arrow-datafusion/issues/686#issuecomment-874368411
> To be specific, if you do to_timestamp(date_string) then it can figure out the timezone from the string, sometimes. However, current architecture of Arrow/DF requires a specific timezone output type. If you did to_timestamp(int64) then you would not have any timezone info at all, and would require the input in the second argument no matter what for completeness. I don't think `to_timestamp(date_string)` should always put the time zone into the data type. It should either never do so and have a second, optional time zone argument (for consistency with the other `to_timestamp` methods) or it should expose a boolean parameter (`keep_timezone` or something like that). The time zone is needed in order to figure out the correct instant. However, it is often not important beyond that. What happens if you have strings from different time zones? -- 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]
