Return-Path: 
 <user-return-29318-apmail-cassandra-user-archive=cassandra.apache.org@cassandra.apache.org>
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 6B1C2D8DD
	for <apmail-cassandra-user-archive@www.apache.org>;
 Wed,  3 Oct 2012 19:00:57 +0000 (UTC)
Received: (qmail 54814 invoked by uid 500); 3 Oct 2012 19:00:54 -0000
Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org
Received: (qmail 54787 invoked by uid 500); 3 Oct 2012 19:00:54 -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 54779 invoked by uid 99); 3 Oct 2012 19:00:54 -0000
Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230)
    by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 03 Oct 2012 19:00:54 +0000
X-ASF-Spam-Status: No, hits=1.5 required=5.0
	tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS
X-Spam-Check-By: apache.org
Received-SPF: pass (nike.apache.org: domain of t.akhayo@gmail.com designates
 74.125.82.42 as permitted sender)
Received: from [74.125.82.42] (HELO mail-wg0-f42.google.com) (74.125.82.42)
    by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 03 Oct 2012 19:00:47 +0000
Received: by mail-wg0-f42.google.com with SMTP id fm10so1433773wgb.1
        for <user@cassandra.apache.org>; Wed, 03 Oct 2012 12:00:27 -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=vd7JJ2npEYp7WR8CTL1BBFiHZpUTKcUzGnFA8J9OzJo=;
        b=rJvo4jPtVGgeimwkDLvxFCeICa5d2xnzvSlaZd8mOdqOPUS7qNAmM9Pi4pG6Ya+sWe
         hJj9/XUjbme665PEAaHg3B14mciXs+ZUsAvRKKpm4sK91NSpBXsdmfs8QrHlbA1hJI3a
         TpIRRqO/83G+Svpi48l5k07SUoMHGu7g0x8I2ju6tnXTeLG3B6o7hiiJJ+dOpweZ5TPX
         32au4FO67Fv9XHTm/dcEutY0WADTZzAPzI/eJcJ+CmVgvDobwdH3tESaF8daZ77fTypY
         XzRbB+YY5yOqOO63W9YEYDV2mcM+npz8JDF+wcPd5Mq86WNqQD5ImqtlwIemtZPLiyit
         8Xmw==
MIME-Version: 1.0
Received: by 10.180.8.134 with SMTP id r6mr31712157wia.18.1349290827057; Wed,
 03 Oct 2012 12:00:27 -0700 (PDT)
Received: by 10.223.86.133 with HTTP; Wed, 3 Oct 2012 12:00:27 -0700 (PDT)
Date: Wed, 3 Oct 2012 21:00:27 +0200
Message-ID: 
 <CAHb4c=FC_W-keHpohRKd1T-POazqm5LTEQm0hDM9WH1gqvVQpw@mail.gmail.com>
Subject: Simple data model for 1 simple range query?
From: T Akhayo <t.akhayo@gmail.com>
To: user@cassandra.apache.org
Content-Type: multipart/alternative; boundary=f46d041827f87209db04cb2c405b

--f46d041827f87209db04cb2c405b
Content-Type: text/plain; charset=ISO-8859-1

Good evening,

I have a quite simple data model. Pseudo CQL code:

create table bars(
timeframe int,
date Date,
info1 double,
info2 double,
..
primary key( timeframe, date )
)

My most important query is (which might be the only one actually):
select * from bars where timeframe=X and date>Y and date <Z

I came to this model because i did read in the past (when 0.7 came out) was
very fast at range queries (using a slice method) when the fields were
keys. And now with cql all the nasty details are hidden ( i have not tested
this yet ;-) )

Is it correct that the above model is a good and fast solution for my query?

Kind regards.

--f46d041827f87209db04cb2c405b
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Good evening,<br><br>I have a quite simple data model. Pseudo CQL code:<br>=
<br>create table bars(<br>timeframe int,<br>date Date,<br>info1 double,<br>=
info2 double,<br>..<br>primary key( timeframe, date )<br>)<br><br>My most i=
mportant query is (which might be the only one actually):<br>
select * from bars where timeframe=3DX and date&gt;Y and date &lt;Z<br><br>=
I came to this model because i did read in the past (when 0.7 came out) was=
 very fast at range queries (using a slice method) when the fields were key=
s. And now with cql all the nasty details are hidden ( i have not tested th=
is yet ;-) )<br>
<br>Is it correct that the above model is a good and fast solution for my q=
uery?<br><br>Kind regards.<br><br>

--f46d041827f87209db04cb2c405b--