Details

    • Type: New Feature
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 2.2.0
    • Component/s: SQL
    • Labels:
    • Target Version/s:

      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

          Issue Links

            Activity

              People

              • Assignee:
                ueshin Takuya Ueshin
                Reporter:
                rxin Reynold Xin
              • Votes:
                3 Vote for this issue
                Watchers:
                21 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: