Return-Path: Delivered-To: apmail-incubator-cassandra-user-archive@minotaur.apache.org Received: (qmail 86535 invoked from network); 20 Jan 2010 20:56:31 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 20 Jan 2010 20:56:31 -0000 Received: (qmail 34675 invoked by uid 500); 20 Jan 2010 20:56:31 -0000 Delivered-To: apmail-incubator-cassandra-user-archive@incubator.apache.org Received: (qmail 34646 invoked by uid 500); 20 Jan 2010 20:56:30 -0000 Mailing-List: contact cassandra-user-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: cassandra-user@incubator.apache.org Delivered-To: mailing list cassandra-user@incubator.apache.org Received: (qmail 34637 invoked by uid 99); 20 Jan 2010 20:56:30 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 20 Jan 2010 20:56:30 +0000 X-ASF-Spam-Status: No, hits=2.8 required=10.0 tests=HTML_FONT_FACE_BAD,HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of driftx@gmail.com designates 209.85.221.180 as permitted sender) Received: from [209.85.221.180] (HELO mail-qy0-f180.google.com) (209.85.221.180) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 20 Jan 2010 20:56:24 +0000 Received: by qyk10 with SMTP id 10so2972309qyk.12 for ; Wed, 20 Jan 2010 12:56:03 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:content-type; bh=Kn0ITxUkY/txDXXjd0YEuCWBoslXKWaGb4H8//QznWM=; b=xA+7utWKtm6+UOMN0VwoMM0HcMYaJBdCM2f7WT1pe6jcNtYhECYOy/4DoeG6x1XCou k49aDVjoZhoENSX0dWuIwqpf1U+mPd2W3KKldZoBIxvE1v7xwQ7+cpBgRtehEwwFpSmj xvFhYRpsa9FtHxsSmqHzZ32Sl80swgRX1Wm0g= 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=fcFkSI2Fi5NhzFt6rlzomV6/0WBGjeqvDzjawXmnWHSbd7gri8yRmfcJpyBDb5v3dT m80SyiE5cmkCKgEXG2V73GFkYXWE3NZ59w1amceMViNPdGW4hTvl2yw3yTNUbScHn5TZ DxPrmzT2RQHgOVt6Z8nm1FZTUhnAQ70BgiHA4= MIME-Version: 1.0 Received: by 10.229.12.212 with SMTP id y20mr340178qcy.16.1264020963229; Wed, 20 Jan 2010 12:56:03 -0800 (PST) In-Reply-To: <91790a981001201231o6e346c2ct4fb687c7799fe431@mail.gmail.com> References: <91790a981001201231o6e346c2ct4fb687c7799fe431@mail.gmail.com> Date: Wed, 20 Jan 2010 14:56:03 -0600 Message-ID: Subject: Re: Cassandra to store logs as a list From: Brandon Williams To: cassandra-user@incubator.apache.org Content-Type: multipart/alternative; boundary=0016364186058081a3047d9ed007 --0016364186058081a3047d9ed007 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable 2010/1/20 S=E9bastien Pierre > Hi there ! > > I only looked briefly at Cassandra, and I would like to know how good it > would be at storing logs. I've been using Redis and its LIST structure to > store JSON-encoded log info, in the following fashion: > > redis["site:0"] =3D ["{'visitor':1,'referer':'http:// > ...'}", "{'visitor':1,'referer':'http://...'}] > > The problem is that the volume of logs is quite big, and would quickly > exhaust the memory on the server and kill performance -- which is why I'm > looking at Cassandra. Hence this question: > would it be possible to store multiple (ordered) values for the same key = in > Cassandra ? > You could handle this equivalently in Cassandra by making the row name 'site:0', using a TimeUUIDType for the column, and JSON serialized data as the value. -Brandon --0016364186058081a3047d9ed007 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
2010/1/20 S=E9bastien Pierre &= lt;sebastien.pierre@gmail.com= >
Hi there !

I only looked briefly at Cassandra= , and I would like to know how good it would be at storing logs. I've b= een using Redis and its LIST structure to store JSON-encoded log info, in t= he following fashion:

redis[&= quot;site:0"] =3D ["{'visitor':1,'referer':'h= ttp://...'}",=A0"{'visitor':1,'referer':'= http://...'}]

The problem is that the volume of logs is quite big, an= d would quickly exhaust the memory on the server and kill performance -- wh= ich is why I'm looking at Cassandra. Hence this question:
would it be possible to store multiple (ordered) values for the same key in= Cassandra ?

You could handle = this equivalently in Cassandra by making the row name 'site:0', usi= ng a TimeUUIDType for the column, and JSON serialized data as the value.

-Brandon
--0016364186058081a3047d9ed007--