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 DD38A9EBE for ; Thu, 5 Jan 2012 05:38:22 +0000 (UTC) Received: (qmail 69076 invoked by uid 500); 5 Jan 2012 05:38:19 -0000 Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org Received: (qmail 68223 invoked by uid 500); 5 Jan 2012 05:38:04 -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 68214 invoked by uid 99); 5 Jan 2012 05:38:01 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 05 Jan 2012 05:38:01 +0000 X-ASF-Spam-Status: No, hits=-0.5 required=5.0 tests=FREEMAIL_ENVFROM_END_DIGIT,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of asdkl93@gmail.com designates 209.85.212.44 as permitted sender) Received: from [209.85.212.44] (HELO mail-vw0-f44.google.com) (209.85.212.44) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 05 Jan 2012 05:37:52 +0000 Received: by vbbfo1 with SMTP id fo1so152930vbb.31 for ; Wed, 04 Jan 2012 21:37:31 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; bh=zX0emfffp1/D5JoLTcGnc41QMw2ML4kEViybmTH+uc4=; b=d77fo7OYMtBlR3SJv4PPlHWyG4DPWiMI3Sao6l6DKuTBX/ojB8iEo6acBKXP3FFUCu Ok6Z7ve/McOgtTTB+CxTE0/aqfqzbngzJ/9qYJ1XcCDu1qLcIjbYpgL9IOVM35w3Jx/N /xcMjUenRTAtdA4BJLsq94p92dswlvoARTBfs= MIME-Version: 1.0 Received: by 10.52.240.144 with SMTP id wa16mr290726vdc.33.1325741851387; Wed, 04 Jan 2012 21:37:31 -0800 (PST) Received: by 10.52.97.161 with HTTP; Wed, 4 Jan 2012 21:37:31 -0800 (PST) Date: Thu, 5 Jan 2012 11:07:31 +0530 Message-ID: Subject: What is the future of supercolumns ? From: Aklin_81 To: user@cassandra.apache.org Content-Type: text/plain; charset=ISO-8859-1 X-Virus-Checked: Checked by ClamAV on apache.org I have seen supercolumns usage been discouraged most of the times. However sometimes the supercolumns seem to fit the scenario most appropriately not only in terms of how the data is stored but also in terms of how is it retrieved. Some of the queries supported by SCs are uniquely capable of doing the task which no other alternative schema could do.(Like recently I asked about getting the equivalent of retrieving a list of (full)supercolumns by name, through use of composite columns, unfortunately there was no way to do this without reading lots of extra columns). So I am really confused whether: 1. Should I really not use the supercolumns for any case at all, however appropriate, or I just need to be just careful while realizing that supercolumns fit my use case appropriately or what!? 2. Are there any performance concerns with supercolumns even in the cases where they are used most appropriately. Like when you need to retrieve the entire supercolumns everytime & max. no of subcolumns vary between 0-10. (I don't write all the subcolumns inside supercolumn, at once though! Does this also matter?) 3. What is their future? Are they going to be deprecated or may be enhanced later?