Github user airhorns commented on the pull request:
https://github.com/apache/spark/pull/6250#issuecomment-103295255
@davies do you think SparkSQL will ever support timezones? This patch means
that round-tripping any timezone aware datetime through SparkSQL will both lose
the original timezone information and return the value timezone naive, which I
think isn't really any better than the current state. I imagine it will be very
surprising and frustrating for developers who aren't intimately familiar with
why Spark might choose to behave this way. What about adding a new rule that
all Dates or Calendars in SparkSQL are converted to UTC before being stored
internally or something like that? Sounds like a performance killer, but don't
Java/Scala devs have this same loss of information issue?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
