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 9C3339696 for ; Mon, 25 Jun 2012 21:10:37 +0000 (UTC) Received: (qmail 82305 invoked by uid 500); 25 Jun 2012 21:10:35 -0000 Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org Received: (qmail 82283 invoked by uid 500); 25 Jun 2012 21:10:35 -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 82269 invoked by uid 99); 25 Jun 2012 21:10:35 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 25 Jun 2012 21:10:35 +0000 X-ASF-Spam-Status: No, hits=2.2 required=5.0 tests=HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: local policy) Received: from [62.109.85.82] (HELO owa.usys.de) (62.109.85.82) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 25 Jun 2012 21:10:24 +0000 Received: from MX0.svu.local ([::1]) by MX0.svu.local ([::1]) with mapi id 14.01.0355.002; Mon, 25 Jun 2012 23:10:02 +0200 From: Henning Kropp To: "user@cassandra.apache.org" Subject: Request Timeout with Composite Columns and CQL3 Thread-Topic: Request Timeout with Composite Columns and CQL3 Thread-Index: Ac1TEhz3LnqruWyRR8CKTsZ9K1w1cQ== Date: Mon, 25 Jun 2012 21:10:01 +0000 Message-ID: Accept-Language: de-DE, en-US Content-Language: de-DE X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [178.25.19.130] Content-Type: multipart/alternative; boundary="_000_F631D967B9FC96498398F69A60A5BB4F0333AC71MX0svulocal_" MIME-Version: 1.0 X-Virus-Checked: Checked by ClamAV on apache.org --_000_F631D967B9FC96498398F69A60A5BB4F0333AC71MX0svulocal_ Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable 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 with strategy_options =3D [{replication_factor:1}] and placement_strategy =3D 'org.apache.cassandra.locator.SimpleStrategy= '; CREATE TABLE logs ( id text, ref text, time bigint, datum text, PRIMARY KEY(id, ref, time) ); I import some data to the table by using a combination of the thrift interf= ace and the hector Composite.class by using its serialization as the column= name: Column col =3D new Column(composite.serialize()); This all seems to work fine until I try to execute the following query whic= h leads to a request timeout: SELECT datum FROM logs WHERE id=3D'861' and ref =3D 'raaf' and time > '3000= '; I really would like to figure out, why running this query on my laptop (sin= gle node, for development) will not finish. I also would like to know if th= e following query would actually work SELECT datum FROM logs WHERE id=3D'861' and ref =3D 'raaf*' and time > '300= 0'; or how else there is a way to define a range for the second component of th= e column key? Any thoughts? Thanks in advance and kind regards Henning --_000_F631D967B9FC96498398F69A60A5BB4F0333AC71MX0svulocal_ Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable

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
with strategy_options =3D [{replication_factor:1}]
and placement_strategy =3D 'org.apache.cassandra.locator= .SimpleStrategy';

CREATE TABLE logs (
id text,
ref text,
time bigint,
datum text,
PRIMARY KEY(id, ref, time)
);

I import some data to the table by using a combination of the thrift interf= ace and the hector Composite.class by using its serialization as the column= name:

Column col =3D new Column(composite.serialize());

This all seems to work fine until I try to execute the following query whic= h leads to a request timeout:

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

I really would like to figure out, why running this query on my laptop (sin= gle node, for development) will not finish. I also would like to know if th= e following query would actually work

SELECT datum FROM logs WHERE id=3D'861' and ref =3D 'raaf*' and time > '= 3000';

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

Any thoughts?

Thanks in advance and kind regards
Henning

--_000_F631D967B9FC96498398F69A60A5BB4F0333AC71MX0svulocal_--