cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Ellis (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (CASSANDRA-6212) TimestampType doesn't support pre-epoch long
Date Thu, 17 Oct 2013 10:33:43 GMT

     [ https://issues.apache.org/jira/browse/CASSANDRA-6212?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Jonathan Ellis updated CASSANDRA-6212:
--------------------------------------

         Reviewer: Aleksey Yeschenko
      Component/s: API
         Priority: Minor  (was: Major)
    Fix Version/s: 2.0.2
         Assignee: Lyuben Todorov

> 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: Lyuben Todorov
>            Priority: Minor
>             Fix For: 2.0.2
>
>
> 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)

Mime
View raw message