You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@cassandra.apache.org by "Jonathan Ellis (JIRA)" <ji...@apache.org> on 2012/09/06 06:42:10 UTC

[jira] [Commented] (CASSANDRA-3929) Support row size limits

    [ https://issues.apache.org/jira/browse/CASSANDRA-3929?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13449412#comment-13449412 ] 

Jonathan Ellis commented on CASSANDRA-3929:
-------------------------------------------

I think we also need to limit

- on flush, since there's no need to knowingly save data we don't want
- on LCR as well as PCR, since enough small rows can still overflow to LCR mode

Also: if I'm understanding correctly, we're tombstoneing the beginning of the row here?  ISTM tombstoning the end of the row will be more in keeping with our advice that "querying from the start of the row in comparator order is fastest."
                
> Support row size limits
> -----------------------
>
>                 Key: CASSANDRA-3929
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-3929
>             Project: Cassandra
>          Issue Type: New Feature
>          Components: Core
>    Affects Versions: 1.2.1
>            Reporter: Jonathan Ellis
>            Assignee: Dave Brosius
>            Priority: Minor
>              Labels: ponies
>             Fix For: 1.2.1
>
>         Attachments: 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