Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Thu, 6 Sep 2012 16:05:10 +1100 (NCT)
From: "Rick Branson (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <1165315598.42968.1346907910797.JavaMail.jiratomcat@arcas>
In-Reply-To: 
 <991877720.51074.1329495359613.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Commented] (CASSANDRA-3929) Support row size limits
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Rick Branson commented on CASSANDRA-3929:
-----------------------------------------

+1 for tombstoning the tail of the row and not the head.

If you want the most recent data at the head of the row, use a ReversedType(TimeUUIDType) comparator. Grabbing the tail on every query will kill performance.
                
> 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