[
https://issues.apache.org/jira/browse/CASSANDRA-3929?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13210354#comment-13210354
]
Jonathan Ellis commented on CASSANDRA-3929:
-------------------------------------------
This is difficult to do efficiently, since it implies checking the entire row's
contents on each update. (Skipping this, and only checking/deleting obsolete
columns at read time, means you could blow your column budget by arbitrarily
large amounts during write intensive workloads.) Even checking randomly on say
1% of writes could dramatically affect write performance for larger-than-memory
datasets.
> 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
> 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
