[ https://issues.apache.org/jira/browse/CASSANDRA-11137?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15261352#comment-15261352 ]
Stefania commented on CASSANDRA-11137: -------------------------------------- Code and tests look good: all dtests passed and failing utests were either unrelated timeouts or also failing on unpatched branches. Committed to 2.2 as 88f22b9692c6fdddf837556f13140d949afe0d28 and up-merged (with -s ours for trunk). Also added a section to NEWS.txt. Test PR closed. > 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 > Assignee: Alex Petrov > Fix For: 3.6, 3.0.6, 2.2.7 > > > 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)