Return-Path: Delivered-To: apmail-cassandra-user-archive@www.apache.org Received: (qmail 81744 invoked from network); 21 Jun 2010 08:33:50 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 21 Jun 2010 08:33:50 -0000 Received: (qmail 58929 invoked by uid 500); 21 Jun 2010 08:33:49 -0000 Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org Received: (qmail 58663 invoked by uid 500); 21 Jun 2010 08:33:46 -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 58655 invoked by uid 99); 21 Jun 2010 08:33:45 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 21 Jun 2010 08:33:45 +0000 X-ASF-Spam-Status: No, hits=2.8 required=10.0 tests=AWL,HTML_MESSAGE,SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (athena.apache.org: local policy) Received: from [209.85.161.172] (HELO mail-gx0-f172.google.com) (209.85.161.172) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 21 Jun 2010 08:33:37 +0000 Received: by gxk6 with SMTP id 6so1597085gxk.31 for ; Mon, 21 Jun 2010 01:33:16 -0700 (PDT) MIME-Version: 1.0 Received: by 10.151.25.6 with SMTP id c6mr4016347ybj.163.1277109196475; Mon, 21 Jun 2010 01:33:16 -0700 (PDT) Received: by 10.151.40.7 with HTTP; Mon, 21 Jun 2010 01:33:16 -0700 (PDT) X-Originating-IP: [80.179.102.198] Date: Mon, 21 Jun 2010 11:33:16 +0300 Message-ID: Subject: Is there a penalty to a SuperColumn? From: David Boxenhorn To: Cassandra Mailing List Content-Type: multipart/alternative; boundary=000e0cd2a05efed5910489862738 --000e0cd2a05efed5910489862738 Content-Type: text/plain; charset=ISO-8859-1 I have a column family that doesn't need to be a supercolumn family right now, but I think it *might* need to be one in the future. I'm considering making it a supercolumn family with only one supercolumn per row to give me flexibility going forward. My question: Is there a penalty to this? If there is, I will make it a regular column family and hope for the best. --000e0cd2a05efed5910489862738 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
I have a column family that doesn't need to be a super= column family right now, but I think it *might* need to be one in the futur= e. I'm considering making it a supercolumn family with only one superco= lumn per row to give me flexibility going forward.

My question: Is there a penalty to this? If there is, I will make it a = regular column family and hope for the best.
--000e0cd2a05efed5910489862738--