cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stefan Podkowinski (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-10397) CQLSH not displaying correct timezone
Date Thu, 11 Feb 2016 14:39:18 GMT


Stefan Podkowinski commented on CASSANDRA-10397:

I've now created a patch for this that would use pytz and tzlocal for automatic timezone conversion.
The code will fallback to UTC in case the modules could not be found:


I'm still wondering about the best way to handle absence of the libs. Users should at least
get a warning in case pytz is missing and a TZ environment value set.

[~pauloricardomg], [~aploetz], any thoughts on that?

> CQLSH not displaying correct timezone
> -------------------------------------
>                 Key: CASSANDRA-10397
>                 URL:
>             Project: Cassandra
>          Issue Type: Bug
>         Environment: Ubuntu 14.04 LTS
>            Reporter: Suleman Rai
>              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

View raw message