[
https://issues.apache.org/jira/browse/CASSANDRA-3929?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13408165#comment-13408165
]
Rick Branson commented on CASSANDRA-3929:
-----------------------------------------
Would love to see this as well, as a way to keep data sizes for wide rows under
control, for use cases where old data at the tail of the row becomes more or
less useless and time is not a dependable dimension to use as a truncation
method.
Clearly it doesn't have to be perfect as far as how much data it actually keeps
around, but I'd like to see the CF configuration be a lower bound on the number
of columns kept. Basically a way to communicate to Cassandra what your
requirement is as far as retention, and it takes care of meeting that target.
An acceptable edge case (at least from my perspective) where this might be
"break" is if the user does their own deletion of some columns.
> Support row size limits
> -----------------------
>
> Key: CASSANDRA-3929
> URL: https://issues.apache.org/jira/browse/CASSANDRA-3929
> Project: Cassandra
> Issue Type: New Feature
> Components: Core
> Reporter: Jonathan Ellis
> Priority: Minor
> Labels: ponies
>
> We currently support expiring columns by time-to-live; we've also had
> requests for keeping the most recent N columns in a row.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
