incubator-cassandra-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Eric Evans <eev...@rackspace.com>
Subject Re: Cassandra Hack-a-thon in Austin
Date Thu, 02 Sep 2010 14:43:18 GMT
On Wed, 2010-08-25 at 09:58 -0500, Eric Evans wrote:
> Some of us from Rackspace are going offsite and heads-down for a day of
> hacking to see how much of the Avro support in Cassandra we can get
> knocked out.  We'll be at Austin Cowork
> (http://www.coworkaustin.com/about.php) on September 1 from 8am to 6pm,
> and we have space enough for 4 more if anyone is interested.
> 
> If you're in the Austin area and would like to join us, shoot me an
> email and give me an idea which area(s) you think you might like to work
> on.  The bigger areas I see are:

So just to follow up, this event happened as planned.  I intended to
send this out yesterday, but it went it so well that by the time I got
back from Austin I was just too tired. :)

There were a total of 8 people who showed up at Cowork yesterday:

* Brandon Williams (Riptano)
* David Strauss (Four Kitchens?)
* Eric Evans (Rackspace)
* Gary Dusbabek (Rackspace)
* Jeremy Hanna (Rackspace)
* Nick Bailey (Rackspace)
* Nirmal Ranganathan (Rackspace)
* Stu Hood (Rackspace)

We got an awful lot done IMO:

* upgraded to avro 1.4.0 release candidate
* multiget_count() rpc implementation
* describe_splits() rpc implementation
* describe_ring() rpc implementation
* check_schema_agreement() rpc implementation
* truncate() rpc implementation
* login() rpc implementation
* get_indexed_slices() rpc implementation
* system_drop_keyspace() rpc implementation
* system_rename_keyspace() rpc implementation
* client state cleanup on deinitializaton (CASSANDRA-1440)
* functional test refactoring
* greater functional test coverage
* some work toward an avro equivalent to py_stress
* and more...

There are also some changesets that were sent to me that I have not yet
had time to merge in, amongst them, a get_range_slices() implementation
that once in will mark 100% API coverage. Yes, 100%. :)

So what's left now? I plan to start filing tickets for the remaining
tasks, but the short answer is that there is still quite a bit left to
do.  We need comprehensive functional test coverage (there are many
holes now), and we need to start evaluating performance.  Some client
work would also be great to see.

Anyway, thanks to everyone that was able to make it yesterday.  It was
definitely worth it from my perspective and I hope to plan another one
Real Soon. :)

-- 
Eric Evans
eevans@rackspace.com


Mime
View raw message