[
https://issues.apache.org/jira/browse/CASSANDRA-11137?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15259946#comment-15259946
]
Stefania commented on CASSANDRA-11137:
--------------------------------------
I'm +1 on the dtest PR, assuming the test team is also OK with using ellipses
to relax the output checks.
We shouldn't backport a patch because of test limitations but, I've noticed
that this ticket is classified as a bug, so back-porting it might be the
correct thing to do after all. Do you agree that it should be back-ported to
2.2 and 3.0, [~iamaleksey] or [~slebresne]?
> 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
>
>
> 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)
