[ https://issues.apache.org/jira/browse/CASSANDRA-6973?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Chander S Pechetty updated CASSANDRA-6973: ------------------------------------------ Attachment: trunk-6973_unittest.txt trunk-6973_v2.txt Good catch on missing non-ISO by removing Z. - Z was only supporting RFC 822 timezone (-0800). - the pattern with two X will cover the RFC 822 which takes care of removing Z. patch v2 takes care of this - pattern with single X covers this ticket (Z as well as -08) - the pattern XXX handles -08:00 - With the one, two and three letter patterns we complete all the 4 timezone designators for 8601 I stated earlier in the ticket - did have a test program, moved that into a unit test and uploaded as a separate patch. On another note maybe its a good idea to rename the iso8601Patterns in TimestampSerializer to something like casTimestampPatterns which cover both iso and non-ISO dates. what do you think ? > 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, trunk-6973_unittest.txt, > trunk-6973_v2.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)