[ 
https://issues.apache.org/jira/browse/TAJO-1419?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14491460#comment-14491460
 ] 

ASF GitHub Bot commented on TAJO-1419:
--------------------------------------

Github user charsyam commented on the pull request:

    https://github.com/apache/tajo/pull/452#issuecomment-92056624
  
    @jihoonson, Thank you for your review :)
    
    There are some problems. 
    Actually, in Tajo,
    
    1.  Client Side Var is not working with ResultSet now.
    Because, getCliSideVar() and getClientSideSessionVars() see different 
vairable map;
    
    2. in "SET TIME ZONE 'GMT+1' case
    It is parsed and executed in Server Side. but in tajo, There is no ability 
to set client side var from server.
    so, currently, SET TIME ZONE commands just set TIMEZONE into Server Side 
Variable.
    
    That's why I just change TIMEZONE as Server Side Var. 
    



> 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)

Reply via email to