[ https://issues.apache.org/jira/browse/CASSANDRA-3929?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13593666#comment-13593666 ]
Jonathan Ellis commented on CASSANDRA-3929: ------------------------------------------- bq. The problem is, say your max_cql_rows is N, and you insert N+1 cql3 rows. And then you delete one of the N first column. Now you are dependent of whether the N+1th row had been deleted by compaction already or not. I see what you mean now; you're right. > 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 > Assignee: Dave Brosius > Priority: Minor > Labels: ponies > Fix For: 2.0 > > Attachments: 3929_b.txt, 3929_c.txt, 3929_d.txt, 3929_e.txt, > 3929_f.txt, 3929_g_tests.txt, 3929_g.txt, 3929.txt > > > 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 For more information on JIRA, see: http://www.atlassian.com/software/jira