Hudson build is back to normal : Cassandra-0.7 #160

2011-01-14 Thread Apache Hudson Server
See

Build failed in Hudson: Cassandra-0.7 #159

2011-01-14 Thread Apache Hudson Server
See Changes: [jake] zero-copy reads Patch by Pavel Yaskevich; Reviewed by Jake Luciani for CASSANDRA-1714 [jake] Fix regression caused by CASSANDRA-1530 patch by Kelvin Kakugawa; reviewed by Jake Luciani for CASSANDRA-1986 ---

Cassandra-Maven-Plugin

2011-01-14 Thread Stephen Connolly
OK, I nearly have the Cassandra-Maven-Plugin ready. It has the following goals: run: launches Cassandra in the foreground and blocks until you press ^C at which point Maven terminates. Use-case: Running integration tests from your IDE. Live development from your IDE. start: launches Cassandr

Re: Proposal: fixed release schedule

2011-01-14 Thread Eric Evans
On Thu, 2011-01-13 at 14:32 -0800, Ryan King wrote: > # Fixed schedule > > We should set a fixed schedule and stick to it. Anything features not > ready at branch time won't make it and will be disabled in the stable > branch. In general, I agree, if we want a cadence, we're going to have to exer

Re: Time for 1.0

2011-01-14 Thread Jeremy Hanna
+1 on starting a more predictable release cycle for Cassandra and doing more multi-node testing. I don't care at all about what version number it is. On Jan 11, 2011, at 7:35 PM, Jonathan Ellis wrote: > Way back in Nov 09, we did a users survey and asked what features > people wanted to see. H

Re: Time for 1.0

2011-01-14 Thread SriSatish Ambati
+1 On making unit tests & distributed tests robust (with & without ec2) Sri On Thu, Jan 13, 2011 at 1:46 PM, Ryan King wrote: > I'm a -1 on naming the next release 1.0 because I don't think it has > the quality that 1.0 implies, but to be honest I don't really care > that much. The version numb

Re: Time for 1.0

2011-01-14 Thread Vijay
+1... Regards, On Tue, Jan 11, 2011 at 5:35 PM, Jonathan Ellis wrote: > Way back in Nov 09, we did a users survey and asked what features > people wanted to see. Here was my summary of the responses: > > http://www.mail-archive.com/cassandra-user@incubator.apache.org/msg01446.html > > Looki

Re: Time for 1.0

2011-01-14 Thread Jonathan Ellis
On Fri, Jan 14, 2011 at 11:24 AM, Ryan King wrote: > On Thu, Jan 13, 2011 at 7:32 PM, Jonathan Ellis wrote: >>... >> In other words, at some point you have so many production users that >> it's silly to pretend it's ready for 1.0.  I'd say we've passed that >> point. > > Did you mean to say "sill

Re: Time for 1.0

2011-01-14 Thread Ryan King
On Thu, Jan 13, 2011 at 7:32 PM, Jonathan Ellis wrote: >... > In other words, at some point you have so many production users that > it's silly to pretend it's ready for 1.0.  I'd say we've passed that > point. Did you mean to say "silly to pretend it's *not* ready for 1.0"? Otherwise, I don't un

Re: Time for 1.0

2011-01-14 Thread Eric Evans
On Thu, 2011-01-13 at 19:20 -0800, Jonathan Ellis wrote: > > -0 > > > > I've said it elsewhere, but the only reason to fuss about a 1.0, is > > that it is loaded with special meaning. > > Right: that's what we should be doing. Up to and including the start > of 0.6 you almost had to have a commi

Re: Send reads concurrently

2011-01-14 Thread altanis
I found the solution to this problem. I was sending the same message to all nodes, with the same ID, and that was apparently causing problems somehow. It is solved anyway. Alexander > Thank you for your answer, however I am pretty sure that's not it. I have > a small-two node cluster for developm