incubator-cassandra-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jonathan Ellis <jbel...@gmail.com>
Subject Re: [DISCUSSION] High-volume counters in Cassandra
Date Fri, 24 Sep 2010 14:03:18 GMT
On Fri, Sep 24, 2010 at 5:39 AM, Torsten Curdt <tcurdt@apache.org> wrote:
> Cassandra is out of incubation and I am no longer on the PMC ...but this
> a little concerning.
>
> I know this discussion is all about good internal design but - for the sake
> of the community - isn't there a way this fork could be avoided? I don't have
> the feeling this is about the work involved implementing it - but
> rather the lack
> of direction or consensus how to implement it.

I am disappointed to see this move by an ASF committer [Johann] rather
than working within the consensus process.  But if it's really
temporary, then I suppose it's not the end of the world.

On the other hand, if the patch authors never bring it up to the
standards of the rest of the project, well, then it's a good thing we
didn't commit it under a "commit now, fix later" process.

> Maybe this fork could be prevented if committers could give the guidance?

While it's true -- and unfortunate, mea culpa -- that the rest of us
weren't involved enough at the beginning of the counter design
process, that's not the case any more.

The people most familiar with this patch besides its authors are
myself and Sylvain, and we have said (starting a month ago) that
building on the Clock structure looks like the wrong approach.  That's
a big change to the patch, so it's understandable that this is painful
for the authors.

-- 
Jonathan Ellis
Project Chair, Apache Cassandra
co-founder of Riptano, the source for professional Cassandra support
http://riptano.com

Mime
View raw message