Return-Path: Delivered-To: apmail-cassandra-user-archive@www.apache.org Received: (qmail 57667 invoked from network); 29 Mar 2010 09:07:25 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 29 Mar 2010 09:07:25 -0000 Received: (qmail 24153 invoked by uid 500); 29 Mar 2010 09:07:24 -0000 Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org Received: (qmail 24014 invoked by uid 500); 29 Mar 2010 09:07:24 -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 24006 invoked by uid 99); 29 Mar 2010 09:07:23 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 29 Mar 2010 09:07:23 +0000 X-ASF-Spam-Status: No, hits=2.2 required=10.0 tests=FREEMAIL_FROM,HTML_MESSAGE,RCVD_IN_DNSWL_NONE,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of skrolle@gmail.com designates 209.85.220.216 as permitted sender) Received: from [209.85.220.216] (HELO mail-fx0-f216.google.com) (209.85.220.216) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 29 Mar 2010 09:07:17 +0000 Received: by fxm8 with SMTP id 8so7062847fxm.25 for ; Mon, 29 Mar 2010 02:06:56 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:received:message-id:subject:from:to:content-type; bh=7pv8/9dhdXb73juPQNH077oz7f+NERAGpsOFxJV6Mj4=; b=BulZFWKUQx1ak0hfFVO4qhx9R3NupEHZKNKktDfKUxaOq0NmzNdAzmMM7PMD5nEWBm xghNKEkmEpUswtT2Im8e+i3+vHYca44Wm0QepItPE48uOcT7LBqslTVH86ew4FYGRhZA AlJ2xU9jtoObAFGhKrKsOHgZTCSEGH7Rbn9fk= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=VBMGt2vqdliKkdg+81NQ1ToXZb37VHkMho23gV51AIz41L70Cxpda0koOqTqcyHIfm Kv2uY+LygwD/s3uU14JxfGQ7xhy1b4btH+oCNky9BkNmOz49TcZEb7Fo/tmUtpIG5WgO 9AqG3VlnTAoYwPhhYeRj22KDJ4+jxjmxfzv7Y= MIME-Version: 1.0 Received: by 10.103.49.7 with HTTP; Mon, 29 Mar 2010 02:06:53 -0700 (PDT) In-Reply-To: References: Date: Mon, 29 Mar 2010 11:06:53 +0200 Received: by 10.102.209.7 with SMTP id h7mr2479544mug.33.1269853613119; Mon, 29 Mar 2010 02:06:53 -0700 (PDT) Message-ID: Subject: Re: Range scan performance in 0.6.0 beta2 From: =?ISO-8859-1?Q?Henrik_Schr=F6der?= To: user@cassandra.apache.org Content-Type: multipart/alternative; boundary=001636416dfb86d8490482ecd510 --001636416dfb86d8490482ecd510 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable On Fri, Mar 26, 2010 at 14:47, Jonathan Ellis wrote: > On Fri, Mar 26, 2010 at 7:40 AM, Henrik Schr=F6der > wrote: > > For each indexvalue we insert a row where the key is indexid + ":" + > > indexvalue encoded as hex string, and the row contains only one column, > > where the name is the object key encoded as a bytearray, and the value = is > > empty. > > It's a unique index then? And you're trying to read things ordered by > the index, not just "give me keys with that have a column with this > value?" > Yes, because if we have more than one column per row, there's no way of (easily) limiting the result. As it is now we rarely want all object keys associated with a range of indexvalues. However, this means we will have a lot of rows if we do it in Cassandra. /Henrik --001636416dfb86d8490482ecd510 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
On Fri, Mar 26, 2010 at 14:47, Jonathan Ellis <jbellis@gmail.com<= /a>> wrote:
On Fri, Mar 26, 2010 at 7:40 AM, Henrik Schr=F6der <skrolle@gmail.com> wrote:
> For each indexvalue we insert a row where the key is indexid + ":= " +
> indexvalue encoded as hex string, and the row contains only one column= ,
> where the name is the object key encoded as a bytearray, and the value= is
> empty.

It's a unique index then? =A0And you're trying to read things= ordered by
the index, not just "give me keys with that have a column with this value?"

Yes, because if we have more than one= column per row, there's no way of (easily) limiting the result. As it = is now we rarely want all object keys associated with a range of indexvalue= s. However, this means we will have a lot of rows if we do it in Cassandra.=


/Henrik
--001636416dfb86d8490482ecd510--