Uploaded image for project: 'Tajo'
  1. Tajo
  2. TAJO-1185

Default timezone should be UTC+0 instead of depending on JVM

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 0.10.0
    • Component/s: None
    • Labels:

      Description

      Background

      Currently, Tajo allows users to set a single global timezone. Since the initial design, the default timezone of a Tajo cluster depends on the JVM timezone if there is no given timezone.

      Problem
      BTW, some of cluster nodes probably can have different timezones due to missed or wrong setting, which actually is usual in practice. It is like to cause wrong results because each task reads and processes a fragment of a single table generated with a single timezone.

      Solution
      In my opinion, the solution is to force Tajo to use an specified timezone instead of depending on JVM timezone. If there is no given timezone, GMT should be used in Tajo cluster.

        Issue Links

          Activity

          Hide
          hyunsik Hyunsik Choi added a comment -

          This issue was just fixed by TAJO-1234.

          Show
          hyunsik Hyunsik Choi added a comment - This issue was just fixed by TAJO-1234 .

            People

            • Assignee:
              Unassigned
              Reporter:
              hyunsik Hyunsik Choi
            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Development