You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@tajo.apache.org by "Hyunsik Choi (JIRA)" <ji...@apache.org> on 2014/12/08 08:51:12 UTC
[jira] [Resolved] (TAJO-1186) Table should have timezone as an
table property
[ https://issues.apache.org/jira/browse/TAJO-1186?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Hyunsik Choi resolved TAJO-1186.
--------------------------------
Resolution: Fixed
Fix Version/s: 0.9.1
This issue was just fixed by TAJO-1234.
> Table should have timezone as an table property
> -----------------------------------------------
>
> Key: TAJO-1186
> URL: https://issues.apache.org/jira/browse/TAJO-1186
> Project: Tajo
> Issue Type: Improvement
> Reporter: Hyunsik Choi
> Assignee: Hyunsik Choi
> Labels: timezone
> Fix For: 0.9.1
>
>
> Currently, Tajo allows only a single global timezone. But, different tables can have different timezones, especially in external tables. Current design does not support this case. So, I propose the timezone table property. We will set the property as follows:
> {noformat}
> CREATE EXTERNAL TABLE T1 (col1 TEXT, col2 TIMESTAMP) WITH ('timezone' = 'Asia/Seoul');
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)