[jira] [Commented] (CASSANDRA-6973) timestamp data type does ISO 8601 formats with 'Z' as time zone.

["Sylvain Lebresne (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/CASSANDRA-6973?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13957634#comment-13957634 ] 

Sylvain Lebresne commented on CASSANDRA-6973:
---------------------------------------------

Hum, I'm not sure at all that's a duplicate of CASSANDRA-6350. And truth is, this should work since it's supposed to be one of the recognized pattern in TimestampSerializer.iso8601Patterns. Not sure what's the problem, but my understanding is that this should work (we certainly pretend to support IS08601 in the doc) and is not really related to CASSANDRA-6350.

> timestamp data type does ISO 8601 formats with 'Z' as time zone.
> ----------------------------------------------------------------
>
>                 Key: CASSANDRA-6973
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-6973
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Core
>            Reporter: Juho Mäkinen
>            Priority: Trivial
>
> The timestamp data type does not support format where time zone is specified with 'Z' (as in zulu aka. UTC+0 aka +0000 time zone). Example:
> create table foo(ts timestamp primary key);
> insert into foo(ts) values('2014-04-01T20:17:35+0000'); -- this works
> cqlsh:test> insert into foo(ts) values('2014-04-01T20:17:35Z');
> Bad Request: unable to coerce '2014-04-01T20:17:35Z' to a  formatted date (long)
> The example date was copied directly from ISO 8601 Wikipedia page. The standard says that "If the time is in UTC, add a Z directly after the time without a space. Z is the zone designator for the zero UTC offset."
> Tested with cqlsh with 2.0.6 version.



--
This message was sent by Atlassian JIRA
(v6.2#6252)