[
https://issues.apache.org/jira/browse/CASSANDRA-10397?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15144825#comment-15144825
]
Stefan Podkowinski commented on CASSANDRA-10397:
------------------------------------------------
It's probably better to add an {{ui.timezone}} option for {{cqlshrc}} that can
be used instead of an command line option and document it along with other
related settings there such as time_format.
I've now updated my branch so the timezone is taken from either {{cqlshrc}},
the {{TZ}} environment value or auto-detected in case {{tzlocal}} is installed,
included warnings in cases Python packages are missing.
> CQLSH not displaying correct timezone
> -------------------------------------
>
> Key: CASSANDRA-10397
> URL: https://issues.apache.org/jira/browse/CASSANDRA-10397
> Project: Cassandra
> Issue Type: Bug
> Environment: Ubuntu 14.04 LTS
> Reporter: Suleman Rai
> Assignee: Stefan Podkowinski
> 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)
