You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Christian Spriegel (JIRA)" <ji...@apache.org> on 2018/01/24 12:58:00 UTC
[jira] [Comment Edited] (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=16337548#comment-16337548 ]
Christian Spriegel edited comment on CASSANDRA-4771 at 1/24/18 12:57 PM:
-------------------------------------------------------------------------
[~rbfblk]: You are a smart guy. It indeed broke 4 years later :)
Edit: I will buy you a beer, should we ever meet ;)
was (Author: christianmovi):
[~rbfblk]: You are a smart guy. It indeed broke 4 years later :)
> 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-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org