cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sylvain Lebresne (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (CASSANDRA-11137) JSON datetime formatting needs timezone
Date Wed, 06 Apr 2016 14:17:25 GMT

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

Sylvain Lebresne updated CASSANDRA-11137:
-----------------------------------------
    Issue Type: Bug  (was: Improvement)

> JSON datetime formatting needs timezone
> ---------------------------------------
>
>                 Key: CASSANDRA-11137
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-11137
>             Project: Cassandra
>          Issue Type: Bug
>          Components: CQL
>            Reporter: Stefania
>
> The JSON date time string representation lacks the timezone information:
> {code}
> cqlsh:events> select toJson(created_at) AS created_at from event_by_user_timestamp
;
>  created_at
> ---------------------------
>  "2016-01-04 16:05:47.123"
> (1 rows)
> {code}
> vs.
> {code}
> cqlsh:events> select created_at FROM event_by_user_timestamp ;
>  created_at
> --------------------------
>  2016-01-04 15:05:47+0000
> (1 rows)
> cqlsh:events>
> {code}
> To make things even more complicated the JSON timestamp is not returned in UTC.
> At the moment {{DateType}} picks this formatting string {{"yyyy-MM-dd HH:mm:ss.SSS"}}.
Shouldn't we somehow make this configurable by users or at a minimum add the timezone?



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

Mime
View raw message