Return-Path: Delivered-To: apmail-cassandra-user-archive@www.apache.org Received: (qmail 81011 invoked from network); 15 Feb 2011 07:19:25 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 15 Feb 2011 07:19:25 -0000 Received: (qmail 90731 invoked by uid 500); 15 Feb 2011 07:19:24 -0000 Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org Received: (qmail 90211 invoked by uid 500); 15 Feb 2011 07:19: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 90203 invoked by uid 99); 15 Feb 2011 07:19:18 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 15 Feb 2011 07:19:18 +0000 X-ASF-Spam-Status: No, hits=4.0 required=5.0 tests=FREEMAIL_FROM,FREEMAIL_REPLY,HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of augustyn.michal@gmail.com designates 209.85.216.44 as permitted sender) Received: from [209.85.216.44] (HELO mail-qw0-f44.google.com) (209.85.216.44) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 15 Feb 2011 07:19:14 +0000 Received: by qwi2 with SMTP id 2so3966689qwi.31 for ; Mon, 14 Feb 2011 23:18:53 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:content-type; bh=IO0oF19Y4Fgbe7flczeMeyghE27zCMahQLiImXsvd7w=; b=vaTXfYZ3dX0OSvbKcUsiWA+yLgWjC71OTHAM3QlDzSzod9J0itWiPsMa77/AJ7SdMr xzNliKR54DMZxt3D2op2TXgK0225ofBjJUNMFn4bO3hTxnvATciZmd636DenlWXAMeZm OdrqHDHIZQ+6tRad1K50DWGu8ofuwVXZhncNQ= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=BbNcYPRdEXk3y1epkHlIB3ho4/W2AQeUsQzxvZh7sJBt0EWCmfRIxOLT0vxEI6XzI8 +ZOelw2agQJqxE3Vqyn1LGI6Hsr2xkudngFhu4NnyT4fJa6M61POXrLR0Z5HSekNFXmK 0h4LvKKXzlyzephjbkKTzHdNRESJADdav/K0o= MIME-Version: 1.0 Received: by 10.229.214.76 with SMTP id gz12mr3723151qcb.8.1297754333048; Mon, 14 Feb 2011 23:18:53 -0800 (PST) Received: by 10.229.246.201 with HTTP; Mon, 14 Feb 2011 23:18:53 -0800 (PST) In-Reply-To: <1193735.1819361297718281806.JavaMail.root@wmail62> References: <1193735.1819361297718281806.JavaMail.root@wmail62> Date: Tue, 15 Feb 2011 08:18:53 +0100 Message-ID: Subject: Re: Backend application for Cassandra From: =?ISO-8859-1?Q?Michal_August=FDn?= To: user@cassandra.apache.org, "cbertu81@libero.it" Content-Type: multipart/alternative; boundary=00163628410c06eead049c4cfae6 --00163628410c06eead049c4cfae6 Content-Type: text/plain; charset=ISO-8859-1 Hi, it depends on your queries complexity - maybe secondary indexes would be sufficient for you - http://www.datastax.com/dev/blog/whats-new-cassandra-07-secondary-indexes If your queries are too complex then you could use Pig (over Hadoop) - http://www.slideshare.net/jeromatron/cassandrahadoop-integration Augi P.S.: I'm just user as you, not Cassandra developer. 2011/2/14 cbertu81@libero.it > Hi all, > I've build a web application using Cassandra. > Data are stored in order to be quickly red/sorted due to my web-app needs. > Everything is working quite good. > Now the big "problem" is that the "other side" of my company needs to > create > reports over these data and the query they need to do would be very "heavy" > in > terms of client-side complexity. > I'd like to know if you have any tips that may help ... I've red something > about Kundera and Lucandra but I don't know these could be solutions ... > > Did you already face problems like this? Could you suggest any valid > product/solution? > I've heard (team-mates) some tips like "export all your CF into a > relational > model and query it" ... and I behaved like i didn't hear it :) > > TIA for any help > > Best Regards > > Carlo > --00163628410c06eead049c4cfae6 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Hi,

it depends on your queries complexity - maybe second= ary indexes would be sufficient for you -=A0http://www.datastax.= com/dev/blog/whats-new-cassandra-07-secondary-indexes

If your queries are too complex then you could use Pig = (over Hadoop) -=A0http://www.slideshare.net/jeromatron/cassandrahadoop-in= tegration

Augi

P.S.: I'm just user a= s you, not Cassandra developer.

2011/2/14= cbertu81@libero.it <cbertu81@libero.it>
Hi all,
I've build a web application using Cassandra.
Data are stored in order to be quickly red/sorted due to my web-app needs.<= br> Everything is working quite good.
Now the big "problem" is that the "other side" of my co= mpany needs to create
reports over these data and the query they need to do would be very "h= eavy" in
terms of client-side complexity.
I'd like to know if you have any tips that may help ... I've red so= mething
about Kundera and Lucandra but I don't know these could be solutions ..= .

Did you already face problems like this? Could you suggest any valid
product/solution?
I've heard (team-mates) some tips like "export all your CF into a = relational
model and query it" ... and I behaved like i didn't hear it :)

TIA for any help

Best Regards

Carlo

--00163628410c06eead049c4cfae6--