Return-Path: 
 <user-return-5220-apmail-cassandra-user-archive=cassandra.apache.org@cassandra.apache.org>
Delivered-To: apmail-cassandra-user-archive@www.apache.org
Received: (qmail 19418 invoked from network); 30 Apr 2010 14:10:07 -0000
Received: from unknown (HELO mail.apache.org) (140.211.11.3)
  by 140.211.11.9 with SMTP; 30 Apr 2010 14:10:07 -0000
Received: (qmail 20283 invoked by uid 500); 30 Apr 2010 14:10:06 -0000
Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org
Received: (qmail 20263 invoked by uid 500); 30 Apr 2010 14:10:06 -0000
Mailing-List: contact user-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:user-help@cassandra.apache.org>
List-Unsubscribe: <mailto:user-unsubscribe@cassandra.apache.org>
List-Post: <mailto:user@cassandra.apache.org>
List-Id: <user.cassandra.apache.org>
Reply-To: user@cassandra.apache.org
Delivered-To: mailing list user@cassandra.apache.org
Received: (qmail 20255 invoked by uid 99); 30 Apr 2010 14:10:06 -0000
Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136)
    by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 30 Apr 2010 14:10:06 +0000
X-ASF-Spam-Status: No, hits=2.5 required=10.0
	tests=AWL,HTML_MESSAGE,RCVD_IN_DNSWL_NONE,SPF_NEUTRAL
X-Spam-Check-By: apache.org
Received-SPF: neutral (athena.apache.org: 74.125.82.172 is neither permitted
 nor denied by domain of utku@topcu.gen.tr)
Received: from [74.125.82.172] (HELO mail-wy0-f172.google.com) (74.125.82.172)
    by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 30 Apr 2010 14:10:00 +0000
Received: by mail-wy0-f172.google.com with SMTP id 35so189467wyb.31
        for <user@cassandra.apache.org>; Fri, 30 Apr 2010 07:09:40 -0700 (PDT)
Received: by 10.216.86.209 with SMTP id w59mr2373411wee.186.1272636578456;
	Fri, 30 Apr 2010 07:09:38 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.216.186.78 with HTTP; Fri, 30 Apr 2010 07:09:18 -0700 (PDT)
In-Reply-To: <k2h709d5bba1004300708i87561ac0ua2cf5495d0d2beee@mail.gmail.com>
References: <h2r709d5bba1004290914vd93de26ai7f90b3312bd3bc3f@mail.gmail.com>
	<v2le06563881004291432k84331b03v747e2b934935a8c4@mail.gmail.com>
	<v2i709d5bba1004291604o5c89ef40kc3c263cb37d0e99c@mail.gmail.com>
	<i2re06563881004300622m81b1ee96wc5a819bc2865dea7@mail.gmail.com>
	<k2h709d5bba1004300708i87561ac0ua2cf5495d0d2beee@mail.gmail.com>
From: =?UTF-8?Q?Utku_Can_Top=C3=A7u?= <utku@topcu.gen.tr>
Date: Fri, 30 Apr 2010 16:09:18 +0200
Message-ID: <l2v709d5bba1004300709sc237750dx72d70dd39374c000@mail.gmail.com>
Subject: Re: ColumnFamilyInputFormat KeyRange scans on a CF
To: user@cassandra.apache.org
Content-Type: multipart/alternative; boundary=0016e6d644c9303fa3048574cbf5

--0016e6d644c9303fa3048574cbf5
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

I meant in the first sentence "running the get_range_slices from a single
point"

On Fri, Apr 30, 2010 at 4:08 PM, Utku Can Top=C3=A7u <utku@topcu.gen.tr> wr=
ote:

> Do you mean, running the get_range_slices from a single? Yes, it would be
> reasonable for a relatively small key range, when it comes to analyze a
> really big range in really big data collection (i.e. like the one we
> currently populate) having a way for distributing the reads among the
> cluster seems the only reasonable solution.
>
> In this current situation, the best option might be distributing the rang=
e
> among ColumnFamilies (say, 1 CF for each day) and emptying the CF in orde=
r
> to reuse for another day range after analyzing the data.
>
> Can you suggest a workaround for this?
>

--0016e6d644c9303fa3048574cbf5
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

I meant in the first sentence &quot;running the get_range_slices from a sin=
gle point&quot;<br><br><div class=3D"gmail_quote">On Fri, Apr 30, 2010 at 4=
:08 PM, Utku Can Top=C3=A7u <span dir=3D"ltr">&lt;<a href=3D"mailto:utku@to=
pcu.gen.tr">utku@topcu.gen.tr</a>&gt;</span> wrote:<br>

<blockquote class=3D"gmail_quote" style=3D"margin: 0pt 0pt 0pt 0.8ex; borde=
r-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">Do you mean, runn=
ing the get_range_slices from a single? Yes, it would be reasonable for a r=
elatively small key range, when it comes to analyze a really big range in r=
eally big data collection (i.e. like the one we currently populate) having =
a way for distributing the reads among the cluster seems the only reasonabl=
e solution.<br>


<br>In this current situation, the best option might be distributing the ra=
nge among ColumnFamilies (say, 1 CF for each day) and emptying the CF in or=
der to reuse for another day range after analyzing the data.<br><br>Can you=
 suggest a workaround for this?<br>

</blockquote></div>

--0016e6d644c9303fa3048574cbf5--