cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dave Brosius (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (CASSANDRA-4771) Setting TTL to Integer.MAX causes columns to not be persisted.
Date Sun, 07 Oct 2012 13:06:04 GMT

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

Dave Brosius edited comment on CASSANDRA-4771 at 10/7/12 1:04 PM:
------------------------------------------------------------------

The value written is delta-ed from the current time as

(System.currentTimeMillis() / 1000) + timeToLive

which causes the written ttl to go negative

the error back to the client could be better, and perhaps pre-flighted.
                
      was (Author: dbrosius@apache.org):
    The value written is delta-ed from the current time as

(System.currentTimeMillis() / 1000) + timeToLive

which causes the written ttl to go negative
                  
> Setting TTL to Integer.MAX causes columns to not be persisted.
> --------------------------------------------------------------
>
>                 Key: CASSANDRA-4771
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-4771
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 1.0.12
>            Reporter: Todd Nine
>            Priority: Blocker
>
> When inserting columns via batch mutation, we have an edge case where columns will be
set to Integer.MAX.  When setting the column expiration time to Integer.MAX, the columns do
not appear to be persisted.
> Fails:
> Integer.MAX_VALUE 
> Integer.MAX_VALUE/2
> Works:
> Integer.MAX_VALUE/3

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message