cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Todd Nine (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (CASSANDRA-4771) Setting TTL to Integer.MAX causes columns to not be persisted.
Date Fri, 05 Oct 2012 19:36:03 GMT

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

Todd Nine updated CASSANDRA-4771:
---------------------------------

    Description: 
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



  was:
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 
Integer.MAX/2

Works:
Integer.MAX/3



    
> 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