Mailing-List: contact cassandra-user-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: cassandra-user@incubator.apache.org
Received-SPF: pass (nike.apache.org: domain of markxr@gmail.com designates
 209.85.219.220 as permitted sender)
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=lZ/FOVBrTEdokKLSkffudSVZcLZDjAVmCja5+BcJHnJCX4yhd8uhOUqN7K56SllR4q
         zYss4NLPoWzJmvj+LTpsIYjc7uwB+j+M1rD8bmFMiycYTRRy/M1iQ+osx/BQpfQZ2Fex
         oiBGrkDaqXT7G8i9tiwpJtJPQ1MhQDzWFK404=
MIME-Version: 1.0
In-Reply-To: <91882eb0911211019i78e6bbet45bfcab3f367d0d6@mail.gmail.com>
References: <e06563880911201317i73c247c8ude7a68fbcdade127@mail.gmail.com>
	 <91882eb0911211019i78e6bbet45bfcab3f367d0d6@mail.gmail.com>
Date: Sat, 21 Nov 2009 19:17:55 +0000
Message-ID: <ff1a07b80911211117n6e2c93e1j99967b00af58d6f5@mail.gmail.com>
Subject: Re: Cassandra users survey
From: Mark Robson <markxr@gmail.com>
To: cassandra-user@incubator.apache.org
Content-Type: multipart/alternative; boundary=000e0cdfd9ec165c460478e67355

--000e0cdfd9ec165c460478e67355
Content-Type: text/plain; charset=ISO-8859-1

We are keeping an eye on Cassandra with a view to using it in a large-scale
audit data application. Currently I don't think it does quite what we want
but I'm still very impressed with what it does do.

We're not yet at the stage of really properly evaluating it for production
use, but I have had a play but only with up to 4 nodes on VMs with little
data. To evaluate it properly I'd need to try it with a lot more nodes on
real hardware with a lot of data; this would require considerable motivation
from the business to loan me the kit (and spare my time from other
activities, of course)

I'd like to see

* More ideas / solutions for the load balancing problem (all my data goes
into a few nodes) - I understand this quite well but find it very difficult
to explain to others
* Bulk delete operations such as the proposed remove_range - or a method of
supplying a timestamp to delete rows after. This is essential for efficient
data purging.

But rather a lot of the things that I wanted from 0.3 have been done
already, thanks.

Mark

--000e0cdfd9ec165c460478e67355
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

We are keeping an eye on Cassandra with a view to using it in a large-scale=
 audit data application. Currently I don&#39;t think it does quite what we =
want but I&#39;m still very impressed with what it does do.<br><br>We&#39;r=
e not yet at the stage of really properly evaluating it for production use,=
 but I have had a play but only with up to 4 nodes on VMs with little data.=
 To evaluate it properly I&#39;d need to try it with a lot more nodes on re=
al hardware with a lot of data; this would require considerable motivation =
from the business to loan me the kit (and spare my time from other activiti=
es, of course)<br>
<br>I&#39;d like to see<br><br>* More ideas / solutions for the load balanc=
ing problem (all my data goes into a few nodes) - I understand this quite w=
ell but find it very difficult to explain to others<br>* Bulk delete operat=
ions such as the proposed remove_range - or a method of supplying a timesta=
mp to delete rows after. This is essential for efficient data purging.<br>
<br>But rather a lot of the things that I wanted from 0.3 have been done al=
ready, thanks.<br><br>Mark<br>

--000e0cdfd9ec165c460478e67355--