[
https://issues.apache.org/jira/browse/TAJO-1419?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14372628#comment-14372628
]
DaeMyung Kang commented on TAJO-1419:
-------------------------------------
This is because of TajoCli has two client side session variable.
one is SessionConnection's sessionVarsCache(Actually TajoResultSetBase tries to
find TIMEZONE value from here.)
another is in TajoCliContext.
and There is another Problem, Tajo SessionVariable can't distinguish
insensitive cases.
1. timezone just is saved as timezone, TajoResultSetBase tries to find
"TIMEZONE"
2. TajoCli pass SessionConnection's sessioVarsCache not TajoCliContext.
3. ClientSide Variables are saved in TajoCliContext.
So, I think there are some solutions.
1. if you want to use TajoCliContext not to communication with TAJO master,
we need merging interface to use this.
or
2. removing ClientSideVar.
Which one is better? [~jihoonson][[~hyunsik]
> 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)
