cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Brandon Williams (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (CASSANDRA-4771) Setting TTL to Integer.MAX causes columns to not be persisted.
Date Mon, 08 Oct 2012 16:14:03 GMT

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

Brandon Williams updated CASSANDRA-4771:
----------------------------------------

    Reviewer: slebresne
    
> 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
>            Priority: Blocker
>             Fix For: 1.2.0 beta 2
>
>         Attachments: 4771.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 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