[
https://issues.apache.org/jira/browse/CASSANDRA-10397?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15147639#comment-15147639
]
Paulo Motta commented on CASSANDRA-10397:
-----------------------------------------
bq. Looks like you missed the timezone constructor argument in trunk:
Fixed this and also included subsecond precision support (CASSANDRA-10428) on
trunk version.
Tests look good now, marking as ready to commit:
Commit info:
- 2.2 patch is compatible with 3.0
- trunk patch is slightly modified due to conflicts
- trunk patch was built on top of CASSANDRA-11135 since it modifies the same
test, so that needs to be committed first.
Thanks for the contribution [~spo...@gmail.com]!
> Add local timezone support to cqlsh
> -----------------------------------
>
> Key: CASSANDRA-10397
> URL: https://issues.apache.org/jira/browse/CASSANDRA-10397
> Project: Cassandra
> Issue Type: Improvement
> Environment: Ubuntu 14.04 LTS
> Reporter: Suleman Rai
> Assignee: Stefan Podkowinski
> Priority: Minor
> Labels: cqlsh
>
> 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)
