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 2B9B510329 for ; Thu, 26 Dec 2013 08:57:29 +0000 (UTC) Received: (qmail 75712 invoked by uid 500); 26 Dec 2013 08:57:23 -0000 Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org Received: (qmail 75665 invoked by uid 500); 26 Dec 2013 08:57:19 -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 75653 invoked by uid 99); 26 Dec 2013 08:57:17 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 26 Dec 2013 08:57:17 +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 (athena.apache.org: domain of efkarr@gmail.com designates 209.85.213.169 as permitted sender) Received: from [209.85.213.169] (HELO mail-ig0-f169.google.com) (209.85.213.169) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 26 Dec 2013 08:57:13 +0000 Received: by mail-ig0-f169.google.com with SMTP id hk11so26939276igb.0 for ; Thu, 26 Dec 2013 00:56:53 -0800 (PST) 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=YPPhFLwJTd+ABkOHRP4Rr3MuZhVMtaeY5qv4EQfYAEI=; b=WnM26x12wbtaTu3H1pNMb0A0QwFcGcr3DXofiXUUqdK7ZVZQrC9+q/l/6TQQtX6tDs Mb1M1Bf8Jfly4Aoj66SMuBEtlJqzMaCVhemK8jSxLARTKj/N0/VPCqAYWRQrNtJNIP8Y ejwG4ZpyBbEWfXIyYpRYYw7lMXoq/qZVCKBbyI8UnqkXaDhpNqFfVCAk7tcHgC7sBFQk K6bOvxIi2SPsIYNc2xljg3UIXC5yElvrhmch3TCkXMf4KEMQYy+gXBKt9bovNQJxF8pC RXWlfb0rp0fx0rinckZj3wR8aiuEZHJ2Xy3aDNRub+0b1/xYgrHYLPvtZkycfphCug75 ShUw== MIME-Version: 1.0 X-Received: by 10.43.71.200 with SMTP id yl8mr42228icb.74.1388048213232; Thu, 26 Dec 2013 00:56:53 -0800 (PST) Received: by 10.43.133.196 with HTTP; Thu, 26 Dec 2013 00:56:53 -0800 (PST) Date: Thu, 26 Dec 2013 10:56:53 +0200 Message-ID: Subject: querying time series from hadoop From: mete To: user@cassandra.apache.org Content-Type: multipart/alternative; boundary=001a11c1e3d4ae51ae04ee6c2866 X-Virus-Checked: Checked by ClamAV on apache.org --001a11c1e3d4ae51ae04ee6c2866 Content-Type: text/plain; charset=ISO-8859-1 Hello folks, i have come up with a basic time series cql schema based on the articles here: http://www.datastax.com/dev/blog/advanced-time-series-with-cassandra so simply put its something like: rowkey, timestamp, col3, col4 etc... where rowkey and timestamp are compound keys. Where i am having issues is to efficiently query this data structure. When i use cqlsh and query it is perfectly fine: select * from table where rowkey='row key' and date > xxx and date <= yyy but when i am using the java driver, the driver already uses row key for token statements and i cannot execute the query above, therefore it does a full scan of rows. The issue that i am having is discussed here: http://stackoverflow.com/questions/19189649/composite-key-in-cassandra-with-pig i have gone through the relevant jira issues 6151 and 6311. This behaviour is supposed to be fixed in 2.0.x but so far it is not there. So now i will try to patch my cassandra 1.2.11 installation but i just wanted to ask you guys first, if there is any other solution that does not involve a release. i assume that this is somewhat a common use case, the articles i referred seems to be old enough and unless i am missing something obvious i cannot query this schema efficiently with the current version (1.2.x or 2.0.x) Does anyone has a similar issue? Any pointers are welcome. Regards Mete --001a11c1e3d4ae51ae04ee6c2866 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Hello =A0folks,=A0

i have come up with = a basic time series cql schema based on the articles here:


so simply put its something like:

<= /div>
rowkey, timestamp, col3, col4 etc...=A0

= where=A0rowkey=A0and timestamp are compound keys.

= Where i am having issues is to efficiently query this data structure.=A0

When i use cqlsh and query it is perfectly fine:
<= div>
select * from table where rowkey=3D'row key' and= date > xxx and date <=3D yyy

but when i am = using the java driver, the driver already uses row key for token statements= and i cannot execute the query above, therefore it does a full scan of row= s.

The issue that i am having is discussed here:


i have gone through the relevant jira issues 6151= and 6311. This behaviour is supposed to be fixed in 2.0.x but so far it is= not there. So now i will try to patch my cassandra 1.2.11 installation but= i just wanted to ask you guys first, if there is any other solution that d= oes not involve a release.

i assume that this is somewhat a common use case, the a= rticles i referred seems to be old enough and unless i am missing something= obvious i cannot query this schema efficiently with the current version (1= .2.x or 2.0.x)

Does anyone has a similar issue? Any pointers are welco= me.

Regards
Mete




--001a11c1e3d4ae51ae04ee6c2866--