Mailing-List: contact cassandra-user-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: cassandra-user@incubator.apache.org
Received-SPF: pass (athena.apache.org: domain of jbellis@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:from:date:message-id:subject:to
         :content-type:content-transfer-encoding;
        b=bVPZpjI1zcK+TO2TleXbyp7jnMA9wwFqMztIWiNP4v+xAcyUk2UKxaeFPSa3GxWLC8
         M9M1uWMubIPizImD8Dichp6AyrqlQh2YEZ4Y7JDZ28MNjiHUte9MlzSwER/fa33260Wj
         tdFjEnA2MQgm/5/GXKShU4/+VAgS6/tZH4YGg=
MIME-Version: 1.0
In-Reply-To: <c9e224d00911241817t47b520bfx5985987eb21434f3@mail.gmail.com>
References: <e06563880911201317i73c247c8ude7a68fbcdade127@mail.gmail.com>
	<c9e224d00911241817t47b520bfx5985987eb21434f3@mail.gmail.com>
From: Jonathan Ellis <jbellis@gmail.com>
Date: Tue, 24 Nov 2009 20:39:19 -0600
Message-ID: <e06563880911241839k3f54471blc4a927796b9f5a23@mail.gmail.com>
Subject: Re: Cassandra users survey
To: cassandra-user@incubator.apache.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

On Tue, Nov 24, 2009 at 8:17 PM, matthew hawthorne <mhawthorne@gmail.com> w=
rote:
> A few desirables for cassandra:
>
> 1) I'm not a huge fan of thrift. =A0it would be nice if the client jar
> came packaged with cassandra =A0(I had to manually build it from the
> thrift-generated java).

It's there, it's just not split out in a separate jar.
org.apache.cassandra.service.Cassandra, etc.  (Probably for someone
better at ant than I, creating a separate cassandra-client.jar for
this would be easy.)

> also, the lack of streaming support is troubling. =A0a lot of our
> internal services are http, and I'd like to be able to connect a
> column's input stream to the output stream of an http response,
> instead of loading it all into memory.

I've mentioned this to Thrift developers, too, but I'm not holding my breat=
h. :)

> 2) a practical/situational view of managing a cassandra cluster
> ...
> it would be nice to have a more comprehensive deployment guide.

You're right.  Maybe we can get Digg to share theirs. :)

> you fellows at Rackspace should consider offering Cassandra support.
> I know that the ability to have some paid professionals come in and
> train our ops team on how to monitor + manage a cassandra cluster
> would have made a huge difference for us.

My impression is that Rackspace is more comfortable with the "we'll
manage your cluster for your" model than the "we'll train you to do it
yourselves" one, but maybe there is room for both.

-Jonathan