[
https://issues.apache.org/jira/browse/CASSANDRA-3929?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13593651#comment-13593651
]
Rick Branson commented on CASSANDRA-3929:
-----------------------------------------
bq. Just wanted to note that when I say that this would "make a good externally
contributed compaction strategy", I also mean that I'm fine generalizing a bit
our current compaction strategy API to make that easier to do (because
currently it's a bit of a pain).
I definitely think making compaction more extensible is quite a useful goal,
and could expand use cases for C*.
It's probably going to be something very simple because our requirements are
pretty loose. We don't need (or even want) deletes and data should get pushed
out pretty quickly. I'm leaning towards simply putting an upper bound on column
count in any given SSTable file produced by compaction. Given that LCS limits
the sprawl of columns across SSTables, I figure the real world p99 is that
we'll have 2x the limit. The target would be to have a mean bloat of 1.5x.
> 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
