[ 
https://issues.apache.org/jira/browse/CASSANDRA-10397?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Suleman Rai updated CASSANDRA-10397:
------------------------------------
    Description: 
CQLSH is not adding the timezone offset to the timestamp after it has been 
inserted into a table.

create table test(id int PRIMARY KEY, time timestamp);
INSERT INTO test(id,time) values (1,dateof(now()));

select *from test;

id | time
----+---------------------
  1 | 2015-09-25 13:00:32

It is just displaying the default UTC timestamp without adding the timezone 
offset. It should be 2015-09-25 21:00:32 in my case as my timezone offset is 
+0800.

  was:
CQLSH is adding the timezone offset to the timestamp after it has been inserted 
into a table.

create table test(id int PRIMARY KEY, time timestamp);
INSERT INTO test(id,time) values (1,dateof(now()));

select *from test;

id | time
----+---------------------
  1 | 2015-09-25 13:00:32

It is just displaying the default UTC timestamp without adding the timezone 
offset. It should be 2015-09-25 21:00:32 in my case as my timezone offset is 
+0800.


> CQLSH not displaying correct timezone
> -------------------------------------
>
>                 Key: CASSANDRA-10397
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-10397
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Core
>         Environment: Ubuntu 14.04 LTS
>            Reporter: Suleman Rai
>            Priority: Blocker
>             Fix For: 2.1.x, 2.2.x
>
>
> CQLSH is not adding the timezone offset to the timestamp after it has been 
> inserted into a table.
> create table test(id int PRIMARY KEY, time timestamp);
> INSERT INTO test(id,time) values (1,dateof(now()));
> select *from test;
> id | time
> ----+---------------------
>   1 | 2015-09-25 13:00:32
> It is just displaying the default UTC timestamp without adding the timezone 
> offset. It should be 2015-09-25 21:00:32 in my case as my timezone offset is 
> +0800.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to