[
https://issues.apache.org/jira/browse/CASSANDRA-6973?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13989541#comment-13989541
]
Sylvain Lebresne commented on CASSANDRA-6973:
---------------------------------------------
It does seems like 'X' is the right thing to do, but won't removing the
patterns with a 'Z' make use refuse date strings (non-ISO 8601 ones) that we
use to accept. Also, why do we need a parttern with 1 'X' and one with 3 'X'
but not, say, with 2 'X' (if that's specified by SimpleDateFormat, this has
escaped me)?
But as a side note, I really wish we weren't doing all this manually. And/or
that we had unit tests for it.
> 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
> Assignee: Chander S Pechetty
> Priority: Trivial
> Attachments: trunk-6973.txt
>
>
> 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)
