[
https://issues.apache.org/jira/browse/TAJO-1419?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14501787#comment-14501787
]
ASF GitHub Bot commented on TAJO-1419:
--------------------------------------
Github user jihoonson commented on the pull request:
https://github.com/apache/tajo/pull/452#issuecomment-94260999
Thanks @charsyam. We had a discussion about the session variable system in
Tajo, and finally found that the variable type of ```TIMEZONE``` should be
```DEFAULT``` rather than ```CLI_SIDE_VAR```.
This patch looks good to me, but I think that it would be great if we have
a test code for this change.
Would you mind adding a test?
> Tsql session command doesn't work
> ---------------------------------
>
> Key: TAJO-1419
> URL: https://issues.apache.org/jira/browse/TAJO-1419
> Project: Tajo
> Issue Type: Bug
> Components: cli
> Reporter: Jihoon Son
> Assignee: DaeMyung Kang
> Fix For: 0.10.1
>
>
> See the title.
> You can reproduce the bug as follows:
> {noformat}
> default> select current_date, current_time();
> ?current_date, ?current_time_1
> -------------------------------
> 2015-03-19, 14:55:39.533999
> (1 rows, 0.043 sec, 0 B selected)
> default>
> default> \set timezone GMT+1
> default> select current_date, current_time();
> ?current_date, ?current_time_1
> -------------------------------
> 2015-03-19, 14:55:55.532
> (1 rows, 0.005 sec, 0 B selected)
> default>
> default> SET TIME ZONE 'GMT+1';
> OK
> default> select current_date, current_time();
> ?current_date, ?current_time_1
> -------------------------------
> 2015-03-19, 06:56:33.213
> (1 rows, 0.005 sec, 0 B selected)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
