[ https://issues.apache.org/jira/browse/CASSANDRA-4771?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Paulo Motta resolved CASSANDRA-4771. ------------------------------------ Resolution: Fixed Normally we don't reopen issues which were already released, the idea is to open a new issue if there is a regression of a previous defect. Since there is CASSANDRA-14092 for the reappearance of this issue I will close this and add a link to this on that ticket. Thanks > 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 > Affects Versions: 1.0.12 > Reporter: Todd Nine > Assignee: Dave Brosius > Priority: Major > 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 (v7.6.3#76005) --------------------------------------------------------------------- To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org