Return-Path: Delivered-To: apmail-cassandra-user-archive@www.apache.org Received: (qmail 40075 invoked from network); 18 Feb 2011 18:30:38 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 18 Feb 2011 18:30:38 -0000 Received: (qmail 47869 invoked by uid 500); 18 Feb 2011 18:30:36 -0000 Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org Received: (qmail 47692 invoked by uid 500); 18 Feb 2011 18:30:34 -0000 Mailing-List: contact user-help@cassandra.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@cassandra.apache.org Delivered-To: mailing list user@cassandra.apache.org Received: (qmail 47684 invoked by uid 99); 18 Feb 2011 18:30:33 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 18 Feb 2011 18:30:33 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,RFC_ABUSE_POST,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of norman.maurer@googlemail.com designates 209.85.210.172 as permitted sender) Received: from [209.85.210.172] (HELO mail-iy0-f172.google.com) (209.85.210.172) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 18 Feb 2011 18:30:27 +0000 Received: by iym1 with SMTP id 1so4061402iym.31 for ; Fri, 18 Feb 2011 10:30:06 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=domainkey-signature:mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:content-type; bh=wUkB2XY/2JqiUsM3M/njt30HFxHtTr5WZUfknpngLoI=; b=IVEchILTvYSDPG/OOVoHfqa843fzXo/rags6+Y4QidX5+vRr6SOHSN/7K0QCH4Q1hj r2CUuf+hIOCtvxni2Od1TZ+5ABRI05iUnSINYTYIvpBqPy38MI00KfPRXk/ri+tZLmWD UO2fvXxC2DaYW72oIHNFFmPSO0ThIZQVVJWto= DomainKey-Signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:content-type; b=oA6PajEjRL6p23ndglna/wSYNPQD9mdAC0RfUxuiS9GToAQ7RTt6GS2PCyJNaEZP4o SCYSNwYCom0llVU6R6XDcZCHAI1rfhGvY0+ZFEHtRwvBiQiAbmVYXK0BUo4xjm4JWdCf feGQThRmYEewufEMgHq/r2+S8dFQG7bclangU= MIME-Version: 1.0 Received: by 10.231.192.73 with SMTP id dp9mr760561ibb.20.1298053806483; Fri, 18 Feb 2011 10:30:06 -0800 (PST) Sender: norman.maurer@googlemail.com Received: by 10.231.13.77 with HTTP; Fri, 18 Feb 2011 10:30:06 -0800 (PST) In-Reply-To: References: Date: Fri, 18 Feb 2011 19:30:06 +0100 X-Google-Sender-Auth: 5eAQIlbMSMiNLBy4yK_iugSF0FQ Message-ID: Subject: Re: managing a limited-length list as a value From: Norman Maurer To: user@cassandra.apache.org Content-Type: text/plain; charset=ISO-8859-1 X-Virus-Checked: Checked by ClamAV on apache.org Hi there, there is not such an operation in cassandra. The only thing which comes "close" is the TTL support which will "delete" columns after a given time. See: http://www.datastax.com/dev/blog/whats-new-cassandra-07-expiring-columns Bye, Norman 2011/2/18 Benson Margulies : > The following is derived from the redis list operations. > > The data model is that a key maps to an list of items. The operation > is to push a new item into the front, and discard any items from the > end above a threshold number of items. > > of course, this can be done by reading a value, fiddling with it, and > writing it back. I write this email to wonder if there's any native > trickery to avoid having to read the value, but rather permitting some > sort of 'push' operation. >