Details
-
New Feature
-
Status: Closed
-
Major
-
Resolution: Fixed
-
None
Description
As of Spark 2.1, Spark SQL assumes the machine timezone for datetime manipulation, which is bad if users are not in the same timezones as the machines, or if different users have different timezones.
We should introduce a session local timezone setting that is used for execution.
An explicit non-goal is locale handling.
Attachments
Attachments
Issue Links
- relates to
-
SPARK-12297 Add work-around for Parquet/Hive int96 timestamp bug.
- Resolved
-
SPARK-15834 Time zone / locale sensitivity umbrella
- Resolved
- links to