[
https://issues.apache.org/jira/browse/TAJO-1234?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14237556#comment-14237556
]
ASF GitHub Bot commented on TAJO-1234:
--------------------------------------
Github user hyunsik commented on the pull request:
https://github.com/apache/tajo/pull/290#issuecomment-66033616
Thank you all guys for the quick review.
@jihoonson TajoConstants.UTC_TIMEZONE is used for a system default config.
In contrast, the unit tests were written to test the behavior of different time
zones. So, I'll change the constant name to SYSTEM_DEFAULT_TIMEZONE.
I'll commit it shortly due to unit test failure. If there are further
feedback, I'll reflect them later in another jira.
> Rearrange timezone in date/time types
> -------------------------------------
>
> Key: TAJO-1234
> URL: https://issues.apache.org/jira/browse/TAJO-1234
> Project: Tajo
> Issue Type: Bug
> Components: data type, planner/optimizer
> Reporter: Hyunsik Choi
> Assignee: Hyunsik Choi
> Priority: Blocker
> Fix For: 0.9.1
>
> Attachments: TAJO-1234.patch, TAJO-1234_2.patch, TAJO-1234_3.patch,
> TAJO-1234_4.patch, TAJO-1234_5.patch, TAJO-1234_6.patch
>
>
> Currently, the master branch causes unit test failures. It's because that
> some inconsistent timezone usages. The main purpose of this issue is to
> cleanup and rearrange timezone usages.
> I discussed this issue with [~jungjw] at
> * http://markmail.org/thread/qhsizgp2pnd6swjq
> * http://markmail.org/message/3nqecl34l2ayxg2x
> I'll fix some parts as I mentioned in above mailing list threads.
> In sum,
> * Tajo will have only four points which consider timezone:
> ** query statement
> ** Input table
> ** text printout in TajoCli
> ** Casting from text to either time or timestamp
> * All other parts have to deal with TIME and TIMESTAMP values as UTC value
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
