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 122B676AC for ; Fri, 11 Nov 2011 13:03:48 +0000 (UTC) Received: (qmail 64274 invoked by uid 500); 11 Nov 2011 13:03:45 -0000 Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org Received: (qmail 64233 invoked by uid 500); 11 Nov 2011 13:03:45 -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 64225 invoked by uid 99); 11 Nov 2011 13:03:45 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 11 Nov 2011 13:03:45 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of the.wa.syndrome@gmail.com designates 209.85.160.172 as permitted sender) Received: from [209.85.160.172] (HELO mail-gy0-f172.google.com) (209.85.160.172) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 11 Nov 2011 13:03:39 +0000 Received: by gye5 with SMTP id 5so3447501gye.31 for ; Fri, 11 Nov 2011 05:03:18 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; bh=5ht1sYNNIncLYM7iPkJQkdCavszwvYztHcX46JtHY2w=; b=tKvGHH+ZuENbPoT91Y9MW+tJD4iqST//SlvKos0PBL3J/xr2LknKJQqcxIA/l/ZSWy H7UNFjoPKS1nm08/li55/X1DYZRgtkVMlq94iGoPn8irkyzYcBsQPzmLZhd7qAEcs9TO NOsYgOviqU1pKQyZwvIUwKRAemFf3pqcaMjV0= MIME-Version: 1.0 Received: by 10.229.68.158 with SMTP id v30mr1732843qci.239.1321016598783; Fri, 11 Nov 2011 05:03:18 -0800 (PST) Received: by 10.229.29.202 with HTTP; Fri, 11 Nov 2011 05:03:18 -0800 (PST) In-Reply-To: References: <4EBCC4BC.4060609@sendmail.cz> Date: Fri, 11 Nov 2011 13:03:18 +0000 Message-ID: Subject: Re: is that possible to add more data structure(key-list) in cassandra? From: =?UTF-8?Q?Filipe_Gon=C3=A7alves?= To: user@cassandra.apache.org Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable You could use composite columns.For example, key: composite(listname:listindex) : value A simple get_range would give you access to list as you would normally have in any programming language, and a "get" could give you direct access to any index. Obviously, this would not be a good fit for list which need insertion at a specific index or reordering... 2011/11/11 Yan Chunlu : > I thought currently no one is maintaining supercolumns related code, and > also it not quite efficient. > > > On Fri, Nov 11, 2011 at 2:46 PM, Radim Kolar wrote: >> >> Dne 11.11.2011 5:58, Yan Chunlu napsal(a): >>> >>> I think cassandra is doing great job on key-value data store, it saved = me >>> tremendous work on maintain the data consistency and service availabili= ty. >>> =C2=A0But I think it would be great if it could support more data struc= tures such >>> as key-list, currently I am using key-value save the list, it seems not= very >>> efficiency. Redis has a good point on this but it is not easy to scale. >>> >>> Maybe it is a wrong place and wrong question, only curious if there is >>> already solution about this, thanks a lot! >> >> use supercolumns unless your lists are very large. > > --=20 Filipe Gon=C3=A7alves