Return-Path: Delivered-To: apmail-cassandra-user-archive@www.apache.org Received: (qmail 53898 invoked from network); 9 Dec 2010 13:44:41 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 9 Dec 2010 13:44:41 -0000 Received: (qmail 44764 invoked by uid 500); 9 Dec 2010 13:44:37 -0000 Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org Received: (qmail 44659 invoked by uid 500); 9 Dec 2010 13:44:37 -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 44509 invoked by uid 99); 9 Dec 2010 13:44:37 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 09 Dec 2010 13:44:37 +0000 X-ASF-Spam-Status: No, hits=2.2 required=10.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (athena.apache.org: local policy) Received: from [209.85.215.171] (HELO mail-ey0-f171.google.com) (209.85.215.171) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 09 Dec 2010 13:44:29 +0000 Received: by eyg5 with SMTP id 5so1639102eyg.30 for ; Thu, 09 Dec 2010 05:44:07 -0800 (PST) MIME-Version: 1.0 Received: by 10.14.37.10 with SMTP id x10mr8474508eea.31.1291902247639; Thu, 09 Dec 2010 05:44:07 -0800 (PST) Received: by 10.14.127.5 with HTTP; Thu, 9 Dec 2010 05:44:07 -0800 (PST) X-Originating-IP: [80.179.102.198] Date: Thu, 9 Dec 2010 15:44:07 +0200 Message-ID: Subject: Secondary indexes change everything? From: David Boxenhorn To: Cassandra Mailing List Content-Type: multipart/alternative; boundary=90e6ba539efa8e34b40496fa6ed1 --90e6ba539efa8e34b40496fa6ed1 Content-Type: text/plain; charset=ISO-8859-1 It seems to me that secondary indexes (new in 0.7) change everything when it comes to data modeling. - OOP becomes obsolete - primary indexes become obsolete if you ever want to do a range query (which you probably will...), better to assign a random row id Taken together, it's likely that very little will remain of your old database schema... Am I right? --90e6ba539efa8e34b40496fa6ed1 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
It seems to me that secondary indexes (new in 0.7) change = everything when it comes to data modeling.

- OOP becomes obsolete - primary indexes become obsolete if you ever want to do a range query (w= hich you probably will...), better to assign a random row id

Taken together, it's likely that very little will remain of your ol= d database schema...

Am I right?
--90e6ba539efa8e34b40496fa6ed1--