Return-Path: X-Original-To: apmail-cassandra-user-archive@www.apache.org Delivered-To: apmail-cassandra-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id AD792DF6F for ; Wed, 10 Oct 2012 09:45:09 +0000 (UTC) Received: (qmail 63935 invoked by uid 500); 10 Oct 2012 09:45:07 -0000 Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org Received: (qmail 63665 invoked by uid 500); 10 Oct 2012 09:45:07 -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 63634 invoked by uid 99); 10 Oct 2012 09:45:06 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 10 Oct 2012 09:45:06 +0000 X-ASF-Spam-Status: No, hits=1.7 required=5.0 tests=FREEMAIL_ENVFROM_END_DIGIT,HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of ertiop93@gmail.com designates 209.85.220.44 as permitted sender) Received: from [209.85.220.44] (HELO mail-pa0-f44.google.com) (209.85.220.44) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 10 Oct 2012 09:44:59 +0000 Received: by mail-pa0-f44.google.com with SMTP id fb11so435039pad.31 for ; Wed, 10 Oct 2012 02:44:38 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=Gw4R4AhfV7WbflgIDxNGlLmqn2L2I8USnwCOw3rqNbo=; b=AWV8wopumIe4MSRKAwPxZb8sbvTcgeVH10Qc91ZW5SbVslyXvUt+cebNNFfrF82/u9 FGXT1CqWR05390y+Ip7BYe3sRle0nKxlqog6YTmRyMNjfb+o7ihAFPTfDoYhCRga/kDC /wZLyQq0gOgBE6GCrJksV4gAl1TkIBFpA36WCZ9XEatg3MqrJgljr8JzcSzCnhgU9IKW d7ClkZvA04AkMRhplV9x0WZIh2OQxIk5t6KiNGCEtB3pjBjqGFoHHUqYD6CIN2EaINBd y/15On35Tf0Bc1jo5666QojfWRN45PqaqnyOKW/Bs9wU2641vQTUnYLtAMPeuFK9uvMy 5O8g== MIME-Version: 1.0 Received: by 10.68.131.35 with SMTP id oj3mr62235052pbb.128.1349862278483; Wed, 10 Oct 2012 02:44:38 -0700 (PDT) Received: by 10.68.31.104 with HTTP; Wed, 10 Oct 2012 02:44:38 -0700 (PDT) In-Reply-To: References: Date: Wed, 10 Oct 2012 15:14:38 +0530 Message-ID: Subject: Re: Option for ordering columns by timestamp in CF From: Ertio Lew To: user@cassandra.apache.org Content-Type: multipart/alternative; boundary=047d7b15ac579ace7a04cbb14da2 --047d7b15ac579ace7a04cbb14da2 Content-Type: text/plain; charset=ISO-8859-1 I think Cassandra should provide an configurable option on per column family basis to do columns sorting by time-stamp rather than column names. This would be really helpful to maintain time-sorted columns without using up the column name as time-stamps which might otherwise be used to store most relevant column names useful for retrievals. Very frequently we need to store data sorted in time order. Therefore I think this may be a very general requirement & not specific to just my use-case alone. Does it makes sense to create an issue for this ? On Fri, Mar 25, 2011 at 2:38 AM, aaron morton wrote: > If you mean order by the column timestamp (as passed by the client) that > it not possible. > > Can you use your own timestamps as the column name and store them as long > values ? > > Aaron > > On 25 Mar 2011, at 09:30, Narendra Sharma wrote: > > > Cassandra 0.7.4 > > Column names in my CF are of type byte[] but I want to order columns by > timestamp. What is the best way to achieve this? Does it make sense for > Cassandra to support ordering of columns by timestamp as option for a > column family irrespective of the column name type? > > > > Thanks, > > Naren > > --047d7b15ac579ace7a04cbb14da2 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable I think Cassandra should provide an configurable option on per column famil= y basis to do columns sorting by=A0time-stamp=A0rather than column names. T= his would be really helpful to maintain=A0time-sorted=A0columns without usi= ng up the column name as=A0time-stamps=A0which might otherwise=A0be used=A0= to store most relevant column names useful for retrievals. Very frequently = we need to store data sorted in time order. Therefore I think this may be a= very general requirement & not specific to just my=A0use-case=A0alone.=

Does it makes sense to create an issue for this ?


On Fri, Mar 25, 2011 at 2:3= 8 AM, aaron morton <aaron@thelastpickle.com> wrote:
If you mean order by the column timestamp (a= s passed by the client) that it not possible.

Can you use your own timestamps as the column name and store them as long v= alues ?

Aaron

On 25 Mar 2011, at 09:30, Narendra Sharma wrote:

> Cassandra 0.7.4
> Column names in my CF are of type byte[] but I want to order columns b= y timestamp. What is the best way to achieve this? Does it make sense for C= assandra to support ordering of columns by timestamp as option for a column= family irrespective of the column name type?
>
> Thanks,
> Naren


--047d7b15ac579ace7a04cbb14da2--