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 EF57CD816 for ; Fri, 21 Sep 2012 00:52:54 +0000 (UTC) Received: (qmail 69030 invoked by uid 500); 21 Sep 2012 00:52:52 -0000 Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org Received: (qmail 68966 invoked by uid 500); 21 Sep 2012 00:52:52 -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 68958 invoked by uid 99); 21 Sep 2012 00:52:52 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 21 Sep 2012 00:52:52 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=FSL_RCVD_USER,HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of cory.p.mintz@gmail.com designates 209.85.212.44 as permitted sender) Received: from [209.85.212.44] (HELO mail-vb0-f44.google.com) (209.85.212.44) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 21 Sep 2012 00:52:45 +0000 Received: by vbbfc26 with SMTP id fc26so3537278vbb.31 for ; Thu, 20 Sep 2012 17:52:24 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=qLxltO8rF9U/axOp1io7ZzgC0cDu2Tj7FstkJzz2anQ=; b=SUCGhE39vyYSPAttj9rYkEcMnGiMjXUMY8aS7bwCqhveoNBReeudmyQUUOqr23r+Xx FMHG5faGcllEzB5RK6bghlvYBQFMB1O5WFsFA9ZfgfBxHY/zq6PFk+bTzb/zGOCD/HxY 5BjAxKSAR7GvxLIqN1C6QNkcTCZVPn+fgY02nKq+Av1WVscN+43UuVMiPQMlcsCZnAmb OSV8nvcThsg3WzFGqWS0mAxxqDYCL86e0IeKpX3N5KPTQ4PxyRbfaRiEfnAyQOXjpZg1 Ss1qCHlzrFcxW4kRnoQCUS9RjV7iuAUfjvmL0dTZQtkKTs+Bsa1/NqyqM3NVNH99mkA2 Ff5g== MIME-Version: 1.0 Received: by 10.220.107.146 with SMTP id b18mr2031900vcp.48.1348188744142; Thu, 20 Sep 2012 17:52:24 -0700 (PDT) Received: by 10.220.226.74 with HTTP; Thu, 20 Sep 2012 17:52:24 -0700 (PDT) Date: Thu, 20 Sep 2012 20:52:24 -0400 Message-ID: Subject: Should row keys be inserted in ascending order? From: Cory Mintz To: user@cassandra.apache.org Content-Type: multipart/alternative; boundary=f46d0438ecff2f4f0c04ca2ba775 --f46d0438ecff2f4f0c04ca2ba775 Content-Type: text/plain; charset=ISO-8859-1 The DataModel page in the Cassandra Wiki ( http://wiki.apache.org/cassandra/DataModel) says: "In Cassandra, each column family is stored in a separate file, and the file is sorted in row (i.e. key) major order." Does this mean that new row keys should be ascending? If they are not ascending does that mean all of the data after the new key needs to be shifted down? Thanks. Cory --f46d0438ecff2f4f0c04ca2ba775 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable

The DataModel page in the Cassandra Wiki (http://wiki.apache.org/cassand= ra/DataModel) says:

=A0

"In Cassandra, each column family is stored in = a separate file, and the file is sorted in row (i.e. key) major order."<= /p>

=A0

Does this mean that ne= w row keys should be ascending? If they are not ascending does that mean al= l

of the data after the new key needs to be shift= ed down?


Thanks.

Cory

--f46d0438ecff2f4f0c04ca2ba775--