[
https://issues.apache.org/jira/browse/CASSANDRA-6212?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13800619#comment-13800619
]
Simon Hopkin commented on CASSANDRA-6212:
-----------------------------------------
Thanks for the quick turnaround on this issue guys.
> TimestampType doesn't support pre-epoch long
> --------------------------------------------
>
> Key: CASSANDRA-6212
> URL: https://issues.apache.org/jira/browse/CASSANDRA-6212
> Project: Cassandra
> Issue Type: Bug
> Components: API, Core
> Reporter: Simon Hopkin
> Assignee: Mikhail Stepura
> Priority: Minor
> Fix For: 2.0.2
>
> Attachments: cassandra-2.0-6212.patch
>
>
> org.apache.cassandra.db.marshal.TimestampType.dateStringToTimestamp()
> contains a regular expression that checks to see if the String argument
> contains a number. If so it parses it as a long timestamp. However
> pre-epoch timestamps are negative and the code doesn't account for this so it
> tries to parse it as a formatted Date. A tweak to the regular expression in
> TimestampType.dateStringToTimestamp() would solve this issue.
> I could use formatted date strings instead, but the TimestampType date parser
> uses ISO8601 patterns which would cause the timestamp to be rounded to the
> nearest second.
> Currently I get the following exception message:
> unable to coerce '-86400000' to a formatted date (long)
--
This message was sent by Atlassian JIRA
(v6.1#6144)
