Mailing-List: contact user-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@cassandra.apache.org
Received-SPF: pass (nike.apache.org: domain of sylvain@datastax.com designates
 209.85.214.172 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <F631D967B9FC96498398F69A60A5BB4F0333AC71@MX0.svu.local>
References: <F631D967B9FC96498398F69A60A5BB4F0333AC71@MX0.svu.local>
Date: Tue, 26 Jun 2012 10:21:00 +0200
Message-ID: 
 <CAKkz8Q0SY+Wcf=1nrKtL5qe-Wty6iNRKF34GskGBMHxjC1TwDA@mail.gmail.com>
Subject: Re: Request Timeout with Composite Columns and CQL3
From: Sylvain Lebresne <sylvain@datastax.com>
To: user@cassandra.apache.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

On Mon, Jun 25, 2012 at 11:10 PM, Henning Kropp <Kropp@nurago.com> wrote:
> Hi,
>
> I am running into timeout issues using composite columns in cassandra 1.1=
.1
> and cql 3.
>
> My keyspace and table is defined as the following:
>
> create keyspace bn_logs
> =A0=A0=A0 with strategy_options =3D [{replication_factor:1}]
> =A0=A0=A0 and placement_strategy =3D 'org.apache.cassandra.locator.Simple=
Strategy';
>
> CREATE TABLE logs (
> =A0 id text,
> =A0 ref text,
> =A0 time bigint,
> =A0 datum text,
> =A0 PRIMARY KEY(id, ref, time)
> );
>
> I import some data to the table by using a combination of the thrift
> interface and the hector Composite.class by using its serialization as th=
e
> column name:
>
> Column col =3D new Column(composite.serialize());
>
> This all seems to work fine until I try to execute the following query wh=
ich
> leads to a request timeout:
>
> SELECT datum FROM logs WHERE id=3D'861' and ref =3D 'raaf' and time > '30=
00';

If it timeouts the likely reason is that this query selects more data
than the machine is able to fetch before the timeout. You can either
add a limit to the query, or increase the timeout.
If that doesn't seem to fix it, it might be worth checking the server
log to see if there isn't an error.

> I really would like to figure out, why running this query on my laptop
> (single node, for development) will not finish. I also would like to know=
 if
> the following query would actually work
>
> SELECT datum FROM logs WHERE id=3D'861' and ref =3D 'raaf*' and time > '3=
000';

It won't. You can perform the following query:

SELECT datum FROM logs WHERE id=3D'861' and ref =3D 'raaf';

which will select every datum whose ref starts with 'raaf', but then
you cannot restrict
the time parameter, so you will get ref where the time is <=3D 3000. Of
course you can
always filter client side if that is an option.

> or how else there is a way to define a range for the second component of =
the
> column key?

As described above, you can define a range on the second component, but the=
n you
won't be able to restrict on the 3rd component.

>
> Any thoughts?
>
> Thanks in advance and kind regards
> Henning
>