You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@cassandra.apache.org by "Randy Fradin (JIRA)" <ji...@apache.org> on 2014/03/13 18:21:48 UTC

[jira] [Commented] (CASSANDRA-4771) Setting TTL to Integer.MAX causes columns to not be persisted.

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

Randy Fradin commented on CASSANDRA-4771:
-----------------------------------------

Isn't this going to break again in less than 4 years when (now + 20 years) > 2038-01-19?

> 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
>            Assignee: Dave Brosius
>             Fix For: 1.1.6
>
>         Attachments: 4771.txt, 4771_b.txt
>
>
> 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 was sent by Atlassian JIRA
(v6.2#6252)