[
https://issues.apache.org/jira/browse/CASSANDRA-4771?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13471560#comment-13471560
]
Sylvain Lebresne commented on CASSANDRA-4771:
---------------------------------------------
I think we'll want to fix that for CQL too (in
ModificationStatement.validate(); and yes, that would be nice to not have
duplication of the validation code but ...). Also, the patch is against trunk,
we should push that to 1.1. Last thing: just returning "ttl too large" doesn't
really help to know why it is too large, and it can be hard to check in the
application that your ttl won't be too large. Maybe it would be simpler to pick
a fixed max TTL value, like say 20 years (which would give us something like 16
years to lift that limitation)?
> 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
