Mailing-List: contact user-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@cassandra.apache.org
Received-SPF: pass (athena.apache.org: domain of sylvain@datastax.com
 designates 209.85.214.172 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <F631D967B9FC96498398F69A60A5BB4F0333D8AB@MX0.svu.local>
References: <F631D967B9FC96498398F69A60A5BB4F0333AC71@MX0.svu.local>
	<CAKkz8Q0SY+Wcf=1nrKtL5qe-Wty6iNRKF34GskGBMHxjC1TwDA@mail.gmail.com>
	<F631D967B9FC96498398F69A60A5BB4F0333D8AB@MX0.svu.local>
Date: Tue, 26 Jun 2012 17:02:21 +0200
Message-ID: 
 <CAKkz8Q3qFg4BdttM9mPjsspdeNEudf5RM5WPpf3O_f4GTWJ+6g@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 Tue, Jun 26, 2012 at 4:00 PM, Henning Kropp <Kropp@nurago.com> wrote:
> Thanks for the reply. Should have thought about looking into the log file=
s sooner. An AssertionError happens at execution. I haven't figured out yet=
 why. Any input is very much appreciated:
>
> ERROR [ReadStage:1] 2012-06-26 15:49:54,481 AbstractCassandraDaemon.java =
(line 134) Exception in thread Thread[ReadStage:1,5,main]
> java.lang.AssertionError: Added column does not sort as the last column
> =A0 =A0 =A0 =A0at org.apache.cassandra.db.ArrayBackedSortedColumns.addCol=
umn(ArrayBackedSortedColumns.java:130)
> =A0 =A0 =A0 =A0at org.apache.cassandra.db.AbstractColumnContainer.addColu=
mn(AbstractColumnContainer.java:107)
> =A0 =A0 =A0 =A0at org.apache.cassandra.db.AbstractColumnContainer.addColu=
mn(AbstractColumnContainer.java:102)
> =A0 =A0 =A0 =A0at org.apache.cassandra.db.filter.SliceQueryFilter.collect=
ReducedColumns(SliceQueryFilter.java:141)
> =A0 =A0 =A0 =A0at org.apache.cassandra.db.filter.QueryFilter.collateColum=
ns(QueryFilter.java:139)
> =A0 =A0 =A0 =A0at org.apache.cassandra.db.CollationController.collectAllD=
ata(CollationController.java:283)
> =A0 =A0 =A0 =A0at org.apache.cassandra.db.CollationController.getTopLevel=
Columns(CollationController.java:63)
> =A0 =A0 =A0 =A0at org.apache.cassandra.db.ColumnFamilyStore.getTopLevelCo=
lumns(ColumnFamilyStore.java:1321)
> =A0 =A0 =A0 =A0at org.apache.cassandra.db.ColumnFamilyStore.getColumnFami=
ly(ColumnFamilyStore.java:1183)
> =A0 =A0 =A0 =A0at org.apache.cassandra.db.ColumnFamilyStore.getColumnFami=
ly(ColumnFamilyStore.java:1118)
> =A0 =A0 =A0 =A0at org.apache.cassandra.db.Table.getRow(Table.java:374)
> =A0 =A0 =A0 =A0at org.apache.cassandra.db.SliceFromReadCommand.getRow(Sli=
ceFromReadCommand.java:69)
> =A0 =A0 =A0 =A0at org.apache.cassandra.service.StorageProxy$LocalReadRunn=
able.runMayThrow(StorageProxy.java:816)
> =A0 =A0 =A0 =A0at org.apache.cassandra.service.StorageProxy$DroppableRunn=
able.run(StorageProxy.java:1250)
> =A0 =A0 =A0 =A0at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(=
ThreadPoolExecutor.java:886)
> =A0 =A0 =A0 =A0at java.util.concurrent.ThreadPoolExecutor$Worker.run(Thre=
adPoolExecutor.java:908)
> =A0 =A0 =A0 =A0at java.lang.Thread.run(Thread.java:662)

Obviously that shouldn't happen. You didn't happen to change the
comparator for the column family or something like that from the
hector side?
Are you able to reproduce from a blank DB?

--
Sylvain

>
>
> BTW: I really would love to understand as of why the combined comparator =
will not allow two ranges be specified for two key parts. Obviously I still=
 lack a profound understanding of cassandras architecture to have a clue.
> And while client side filtering might seem like a valid option I am still=
 trying to get might head around a cassandra data model that would allow th=
is.
>
> best regards
>
> ________________________________________
> Von: Sylvain Lebresne [sylvain@datastax.com]
> Gesendet: Dienstag, 26. Juni 2012 10:21
> Bis: user@cassandra.apache.org
> Betreff: Re: Request Timeout with Composite Columns and CQL3
>
> 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 with strategy_options =3D [{replication_factor:1}]
>> =A0 =A0 and placement_strategy =3D 'org.apache.cassandra.locator.SimpleS=
trategy';
>>
>> 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 t=
he
>> column name:
>>
>> Column col =3D new Column(composite.serialize());
>>
>> This all seems to work fine until I try to execute the following query w=
hich
>> leads to a request timeout:
>>
>> SELECT datum FROM logs WHERE id=3D'861' and ref =3D 'raaf' and time > '3=
000';
>
> 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 kno=
w if
>> the following query would actually work
>>
>> SELECT datum FROM logs WHERE id=3D'861' and ref =3D 'raaf*' and time > '=
3000';
>
> 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 t=
hen you
> won't be able to restrict on the 3rd component.
>
>>
>> Any thoughts?
>>
>> Thanks in advance and kind regards
>> Henning
>>