Re: Login Failure
On Wed, 2010-03-10 at 16:31 +0100, Morten Wegelbye Nissen wrote: > After the latest patch in the auth I saw the same. I needed to supply > the --keyspace, --username and --password. (funny thing is that with > the "allow all" authentication its still mandatory. Gah, you're right. > # cassandra-cli --host localhost --port 9160 --keyspace Keyspace1 > --username mickey --password mouse > Starting Cassandra Client > Connected to: "Morten's MEGA Cluster" on localhost/9160 > Welcome to cassandra CLI. > > Type 'help' or '?' for help. Type 'quit' or 'exit' to quit. > cassandra> > > Works fine (user mickey is not defined anywhere). > > Question is, is this a bug or a feature? If bug, I can go for the > patch, if feature the wiki should be updated. Well, it's a bug introduced while introducing support for a half-baked feature. CASSANDRA-852 added support for the Thrift login() method which is present and usable in 0.6, but optional, (though obviously it implemented that in a way that made it non-optional). For 0.7, login() will become mandatory, even if you've effectively disabled authentication (it will be used to set a current working keyspace, and the keyspace argument will be dropped from the other methods). So, it's buggy for 0.6, and trunk, and the direction trunk is going in, but to different degrees and for different reasons :) I've reopened CASSANDRA-852 and attached a patch for 0.6 that makes the invocation of login() conditional on the all three of the new arguments (keyspace, username, and password). https://issues.apache.org/jira/browse/CASSANDRA-852 -- Eric Evans eev...@rackspace.com
Re: Further enhancments in j.a.c.auth
On Tue, 2010-03-09 at 16:19 -0600, Jonathan Ellis wrote: > We should probably use http://www.mindrot.org/projects/jBCrypt/. > (Lots of background: > http://chargen.matasano.com/chargen/2007/9/7/enough-with-the-rainbow-tables-what-you-need-to-know-about-s.html) > > We kind of have a nagging feeling though that rolling our own auth > framework in 2010 is the wrong approach. > http://en.wikipedia.org/wiki/Simple_Authentication_and_Security_Layer > has been mentioned as an alternative. My understanding is that Avro will ultimately support two different transports, HTTP, and a yet-to-be-specified socket-based protocol that will include support for SASL. Obviously that's vaporware on top of vaporware at the moment, but having authentication pushed into the transport in an extensible way seems like a pretty good answer (if/when we get there of course). Just something to think about. -- Eric Evans eev...@rackspace.com
Re: Login Failure
On Wed, 2010-03-10 at 19:24 +0530, shirish wrote: > and next i ran* cassandra-cli --host 127.0.0.1 --port 9160* I get the > following > > Login failure. Did you specify 'keyspace', 'username' and 'password'? > Welcome to cassandra CLI. > > Type 'help' or '?' for help. Type 'quit' or 'exit' to quit. > > > What could have gone wrong ? Were there any exceptions produced by the node (i.e. in the terminal where you started cassandra in the foreground)? Try adding the --debug argument when starting cassandra-cli, that should cause it to print a stacktrace when the error occurs. -- Eric Evans eev...@rackspace.com
Re: Maven support in 0.6 and beyond?
On Tue, 2010-03-02 at 10:46 -0800, Nathan McCall wrote: > I noticed the pom file was missing in the 0.6 branch, but still > available in trunk. The pom.xml should be in contrib/maven on both 0.6 and trunk. > Is this an oversight or is the focus going to be on ant going > forward? The focus has only ever been on ant, (most of the committers opinions range somewhere between "apathy" and "abject disgust" when it comes to maven). The pom.xml was contributed by someone who wanted it, and hasn't ever been very well maintained TTBMK. -- Eric Evans eev...@rackspace.com
[VOTE RESULTS] was: [VOTE] Release 0.5.1
On Tue, 2010-02-23 at 17:27 -0600, Eric Evans wrote: > There have been some important bug fixes[1] in the 0.5 branch since we > released. Plus, I thought it would be cool to conduct two separate > release votes at the time. :) > > I propose the following tag and artifacts for 0.5.1: The vote passes with 3 binding and 2 others. Thanks! > SVN Tag: > https://svn.apache.org/repos/asf/incubator/cassandra/tags/cassandra-0.5.1 > 0.5.1 artifacts: http://people.apache.org/~eevans > > +1 from me. > > > [1] > https://svn.apache.org/repos/asf/incubator/cassandra/tags/cassandra-0.5.1/CHANGES.txt -- Eric Evans eev...@rackspace.com
[VOTE RESULTS] was: [VOTE] Release 0.6.0-beta2
On Tue, 2010-02-23 at 13:36 -0600, Eric Evans wrote: > There has been a lot of cool work done since our last release[1] (0.5.0), > and while there's still a bit more to be done[2], the dust is settling on > all of the big stuff. Now seems like a good time for a beta release. > > I propose the following tag and artifacts for 0.6.0-beta2[3]: The vote passes with 4 binding, and 4 others. Thanks! > SVN Tag: > https://svn.apache.org/repos/asf/incubator/cassandra/tags/cassandra-0.6.0-beta2 > 0.6.0-beta2 artifacts: http://people.apache.org/~eevans > > +1 from me. > > > [1] > https://svn.apache.org/repos/asf/incubator/cassandra/tags/cassandra-0.6.0-beta2/CHANGES.txt > [2] https://issues.apache.org/jira/browse/CASSANDRA/fixforversion/12314361 > [3] beta1 was an aborted attempt so we're jumping straight to beta2, > sorry about that. -- Eric Evans eev...@rackspace.com
Re: [VOTE] Release 0.5.1
On Wed, 2010-02-24 at 13:50 -0800, Masood Mortazavi wrote: > fwiw ... cli says the version number hasn't changed on this ... it still > report 0.5.0 ... Are you sure you're not connecting to a node that is running 0.5.0? -- Eric Evans eev...@rackspace.com
[VOTE] Release 0.5.1
There have been some important bug fixes[1] in the 0.5 branch since we released. Plus, I thought it would be cool to conduct two separate release votes at the time. :) I propose the following tag and artifacts for 0.5.1: SVN Tag: https://svn.apache.org/repos/asf/incubator/cassandra/tags/cassandra-0.5.1 0.5.1 artifacts: http://people.apache.org/~eevans +1 from me. [1] https://svn.apache.org/repos/asf/incubator/cassandra/tags/cassandra-0.5.1/CHANGES.txt -- Eric Evans eev...@rackspace.com
Re: [VOTE] Release 0.6.0-beta2
On Tue, 2010-02-23 at 13:36 -0600, Eric Evans wrote: > I propose the following tag and artifacts for 0.6.0-beta2[3]: > > SVN Tag: > https://svn.apache.org/repos/asf/incubator/cassandra/tags/cassandra-0.6.0-beta2 > 0.6.0-beta2 artifacts: http://people.apache.org/~eevans It's been pointed out that there were only artifacts for 0.6.0-beta1. That was (yet another )mistake on my part. Those files were in fact for the `cassandra-0.6.0-beta2' tag and I have since uploaded correctly named artifacts. Sorry for any confusion. -- Eric Evans eev...@rackspace.com
[VOTE] Release 0.6.0-beta2
There has been a lot of cool work done since our last release[1] (0.5.0), and while there's still a bit more to be done[2], the dust is settling on all of the big stuff. Now seems like a good time for a beta release. I propose the following tag and artifacts for 0.6.0-beta2[3]: SVN Tag: https://svn.apache.org/repos/asf/incubator/cassandra/tags/cassandra-0.6.0-beta2 0.6.0-beta2 artifacts: http://people.apache.org/~eevans +1 from me. [1] https://svn.apache.org/repos/asf/incubator/cassandra/tags/cassandra-0.6.0-beta2/CHANGES.txt [2] https://issues.apache.org/jira/browse/CASSANDRA/fixforversion/12314361 [3] beta1 was an aborted attempt so we're jumping straight to beta2, sorry about that. -- Eric Evans eev...@rackspace.com
Re: 0.6, 0.7, and the future
On Wed, 2010-02-17 at 15:32 -0600, Jonathan Ellis wrote: > So what I'd like to propose is making 0.7 primarily about the > internals changes and push for high-level queries in 0.8, where both > of those hit our usual ~3 month release cycle. I don't think it makes > sense to do those the other way around; introducing new APIs that we > already know we need to break just seems mean. :) I think this makes sense. +1 -- Eric Evans eev...@rackspace.com
[VOTE RESULTS] was: [VOTE] release cassandra 0.5.0 (final)
On Tue, 2010-01-19 at 20:11 -0600, Eric Evans wrote: > The Cassandra community voted on and approved the release of Apache > Cassandra 0.5.0. We would now like to request the approval of the > Incubator PMC for this release. > > Cassandra is a massively scalable, eventually consistent, distributed, > structured key-value store. > > Podling vote thread: http://thread.gmane.org/gmane.comp.db.cassandra.devel/811 > 0.5.0 artifacts: http://people.apache.org/~eevans > SVN tag: > https://svn.apache.org/repos/asf/incubator/cassandra/tags/cassandra-0.5.0 > Project home: http://incubator.apache.org/cassandra/ > Incubation status: http://incubator.apache.org/projects/cassandra.html > > We received three (IPMC )binding votes[1][2][3] during the poddling vote, > but help with artifact review is always welcome. > > The vote will remain open for 72 hours. > > Regards, > The vote is now closed with the following tally: * +1 votes: 3 (Ian Holsman, Matthieu Riou, ant elder) * 0 votes: 0 * -1 votes: 0 The vote passes. Thanks to everyone that reviewed the release. > [1] http://article.gmane.org/gmane.comp.db.cassandra.devel/814 > [2] http://article.gmane.org/gmane.comp.db.cassandra.devel/820 > [3] http://article.gmane.org/gmane.comp.db.cassandra.devel/825 -- Eric Evans eev...@rackspace.com
[VOTE] release cassandra 0.5.0 (final)
The Cassandra community voted on and approved the release of Apache Cassandra 0.5.0. We would now like to request the approval of the Incubator PMC for this release. Cassandra is a massively scalable, eventually consistent, distributed, structured key-value store. Podling vote thread: http://thread.gmane.org/gmane.comp.db.cassandra.devel/811 0.5.0 artifacts: http://people.apache.org/~eevans SVN tag: https://svn.apache.org/repos/asf/incubator/cassandra/tags/cassandra-0.5.0 Project home: http://incubator.apache.org/cassandra/ Incubation status: http://incubator.apache.org/projects/cassandra.html We received three (IPMC )binding votes[1][2][3] during the poddling vote, but help with artifact review is always welcome. The vote will remain open for 72 hours. Regards, [1] http://article.gmane.org/gmane.comp.db.cassandra.devel/814 [2] http://article.gmane.org/gmane.comp.db.cassandra.devel/820 [3] http://article.gmane.org/gmane.comp.db.cassandra.devel/825 -- Eric Evans eev...@rackspace.com
[VOTE] Release 0.5.0 (final)
There have been a few changes[1] in the 0.5 branch since RC3. In a perfect world, we'd probably push those into another release candidate, but I feel pretty good about this one, and any remaining issues can always be added to 0.5.1. I propose the following tag and artifacts for 0.5.0: SVN Tag: https://svn.apache.org/repos/asf/incubator/cassandra/tags/cassandra-0.5.0 0.5.0 artifacts: http://people.apache.org/~eevans +1 from me. [1] https://svn.apache.org/repos/asf/incubator/cassandra/tags/cassandra-0.5.0/CHANGES.txt -- Eric Evans eev...@rackspace.com
Re: API versioning
On Wed, 2010-01-06 at 16:55 -0600, Eric Evans wrote: > On Wed, 2010-01-06 at 16:33 -0600, Denny Abraham wrote: > > This seems similar enough to the semantic versioning spec > > http://semver.org/. (minus the third value) that it may be convenient > > and worthwhile to implement the full spec. > > The third value here is for "backward compatible bug fixes", (as others > here have suggested). The wording on the page eludes to changes that > "fix incorrect behavior", or "these are changes that could create > problems if the library relied on buggy behavior" (my words). > > I can get on board with that. > > So that would make, x.y.z where x is major, y is minor, and z is patch > level. The major is bumped for breaking changes, the minor is bumped for > changes in features or functionality that are backward compatible, and > the patch level is bumped for every other change. > FYI, this was put in place in CASSANDRA-686. The current API version is now "1.0.0". Thanks everyone. -- Eric Evans eev...@rackspace.com
[VOTE RESULTS] was: [VOTE] release cassandra 0.5.0-rc3
On Thu, 2010-01-07 at 11:26 -0600, Eric Evans wrote: > Podling vote thread: http://thread.gmane.org/gmane.comp.db.cassandra.devel/764 > 0.5.0-rc3 artifacts: http://people.apache.org/~eevans > SVN tag: > https://svn.apache.org/repos/asf/incubator/cassandra/tags/cassandra-0.5.0-rc3 > Project home: http://incubator.apache.org/cassandra/ > Incubation status: http://incubator.apache.org/projects/cassandra.html > > We received one (IPMC )binding vote[1] during the poddling vote, so we'll > need at least a couple more here. > > The vote will remain open for 72 hours (or longer if needed). > > Regards, > > [1] http://article.gmane.org/gmane.comp.db.cassandra.devel/766 The vote is now closed with the following tally: * +1 votes: 4 (Matthieu Riou, ant elder, Ian Holsman, and Matt Hogstrom) * 0 votes: 0 * -1 votes: 0 The votes passes. Thanks to everyone who reviewed and voted. Your help, as always, is appreciated. -- Eric Evans eev...@rackspace.com
Re: release policy
On Fri, 2010-01-08 at 13:47 -0600, Jonathan Ellis wrote: [ ... ] > Thoughts? (Separate threads to follow re "the next major release > after 0.5 specifically," and "1.0.") I'd be curious to hear from the Digg guys. My understanding is that they've been doing a considerable amount of custom release work, backporting patches into snapshots and the like. Is that still true? What would it take to remain more in-sync cassandra releases? -- Eric Evans eev...@rackspace.com
[VOTE] release cassandra 0.5.0-rc3
The Cassandra community voted on and approved the release of Apache Cassandra 0.5.0-rc3. We would now like to request the approval of the Incubator PMC for this release. Cassandra is a massively scalable, eventually consistent, distributed, structured key-value store. Podling vote thread: http://thread.gmane.org/gmane.comp.db.cassandra.devel/764 0.5.0-rc3 artifacts: http://people.apache.org/~eevans SVN tag: https://svn.apache.org/repos/asf/incubator/cassandra/tags/cassandra-0.5.0-rc3 Project home: http://incubator.apache.org/cassandra/ Incubation status: http://incubator.apache.org/projects/cassandra.html We received one (IPMC )binding vote[1] during the poddling vote, so we'll need at least a couple more here. The vote will remain open for 72 hours (or longer if needed). Regards, [1] http://article.gmane.org/gmane.comp.db.cassandra.devel/766 -- Eric Evans eev...@rackspace.com
Re: API versioning
On Wed, 2010-01-06 at 16:33 -0600, Denny Abraham wrote: > This seems similar enough to the semantic versioning spec > http://semver.org/. (minus the third value) that it may be convenient > and worthwhile to implement the full spec. The third value here is for "backward compatible bug fixes", (as others here have suggested). The wording on the page eludes to changes that "fix incorrect behavior", or "these are changes that could create problems if the library relied on buggy behavior" (my words). I can get on board with that. So that would make, x.y.z where x is major, y is minor, and z is patch level. The major is bumped for breaking changes, the minor is bumped for changes in features or functionality that are backward compatible, and the patch level is bumped for every other change. -- Eric Evans eev...@rackspace.com
Re: API versioning
On Thu, 2010-01-07 at 08:41 +1100, Ian Holsman wrote: > can you add a new method api_version? > some people will probably still want to know the version of the > software being run, and it is still useful info to have for > operational issues. Yeah, you could, and that was what I had in mind initially. The conclusion I came to though was that with a properly versioned API, the software version was really only of interest to operations, and that it would be better published along with the rest of our management info, (via JMX). > +1 on the numbering scheme. > > as for breaking something that works (ie a client library), you can > make the client library just have a 'SUPPORTED_VERSION' api call and a > 'reported_version' api call, and let the application decide. Sure. -- Eric Evans eev...@rackspace.com
Re: API versioning
On Wed, 2010-01-06 at 13:40 -0800, Anthony Molinaro wrote: > > What would be the rules governing that 3rd value? > > I usually like the first to be non-compatible changes, the second > to be new functionality which is backward compatible and the third > to be bugfixes. In the case of the .thrift file the third value > might be for adding comments or something like that. Comments aren't accessible to the client; I'm not sure I see the point in exposing that remotely. -- Eric Evans eev...@rackspace.com
Re: API versioning
On Wed, 2010-01-06 at 14:29 -0600, Jonathan Ellis wrote: > > One question: do we need a 3-tuple? What would be the rules governing that 3rd value? > The 0.5 api is a superset of the 0.4 one in method names and > arguments, but the exceptions declared are different, so client code > in compiled languages with checked exceptions (only Java?) probably > needed some light editing to upgrade. That still breaks existing code though. Would you not bump the major for such a case? -- Eric Evans eev...@rackspace.com
API versioning
I'd like to propose a change to the way we version our API.
Currently, we publish a version string via the thrift method
get_string_property("version"). This version string always moves in
lock-step with the current release, i.e. 0.4.0-beta2, 0.5.0-rc3, etc.
There is no useful correlation that can be made like this. If a client
API worked with 0.5.0-beta1, it might or might not work with
0.5.0-beta2. I think we can do better.
I propose that we return a string composed of joining two integers with
a ".", where the integers represent a major and minor respectively. The
rules for incrementing these would be simple:
1. If it is absolutely breaking, then the major is incremented by one.
For example, changing the number or disposition of required arguments.
2. If it will result in an API that is backward-compatible with the
previous version, then the minor is incremented. For example, if a new
method is added.
This would provide client API authors the tools necessary to ensure
compatibility at runtime, and to better manage the life-cycle of their
projects.
What does everyone think?
--
Eric Evans
eev...@rackspace.com
[VOTE] Release 0.5.0-rc3
Ok let's try this again, this time with the actual fix for #663. :) I propose the following tag and artifacts for 0.5.0-rc3: SVN Tag: https://svn.apache.org/repos/asf/incubator/cassandra/tags/cassandra-0.5.0-rc3 0.5.0-rc3 artifacts: http://people.apache.org/~eevans +1 from me. [1] https://svn.apache.org/repos/asf/incubator/cassandra/tags/cassandra-0.5.0-rc3/CHANGES.txt -- Eric Evans eev...@rackspace.com
Chair
When we graduate, we need to have someone who will act as the Chair of the Project Management Committee, or "Chair". The Chair reports to the ASF Board on behalf of the project, maintains information on the PMC disposition, provides write access to new committers, etc. So besides sounding kind of prestigious, the Chair is basically a glorified administrative assistant. :) http://www.apache.org/dev/pmc.html#chair My understanding is that the Chair a) needs to be on the PMC[1], and b) must volunteer for the job. So, do we have any volunteers? Jonathan (hint, hint :)? [1] http://incubator.apache.org/projects/cassandra.html#Project+info -- Eric Evans eev...@rackspace.com
[VOTE] Release 0.5.0-rc2
There were some issues in rc1 that warrant us taking another stab at this, (see [1]). I propose the following tag and artifacts for 0.5.0-rc2: SVN Tag: https://svn.apache.org/repos/asf/incubator/cassandra/tags/cassandra-0.5.0-rc2 0.5.0-rc2 artifacts: http://people.apache.org/~eevans +1 from me. [1] https://svn.apache.org/repos/asf/incubator/cassandra/tags/cassandra-0.5.0-rc2/CHANGES.txt -- Eric Evans eev...@rackspace.com
Re: Welcome new committers Gary Dusbabek and Jaakko Laine!
On Wed, 2009-12-30 at 15:19 -0600, Jonathan Ellis wrote: > Thanks for the help, guys! Hurray! -- Eric Evans eev...@rackspace.com
[VOTE] release cassandra 0.5.0-rc1
The Cassandra community voted on and approved the release of Apache Cassandra 0.5.0-rc1. We would now like to request the approval of the Incubator PMC for this release. Cassandra is a massively scalable, eventually consistent, distributed, structured key-value store. Podling vote thread: http://thread.gmane.org/gmane.comp.db.cassandra.devel/728 0.5.0-rc1 artifacts: http://people.apache.org/~eevans SVN tag: https://svn.apache.org/repos/asf/incubator/cassandra/tags/cassandra-0.5.0-rc1 Project home: http://incubator.apache.org/cassandra/ Incubation status: http://incubator.apache.org/projects/cassandra.html We received only one (IPMC )binding vote[1] during the poddling vote, so we'll need two more. Any help with reviewing/voting from outside our mentors list would be appreciated. The vote will remain open for 72 hours (or longer if needed). Regards, [1] http://article.gmane.org/gmane.comp.db.cassandra.devel/734 -- Eric Evans eev...@rackspace.com
[VOTE] Release 0.5.0-rc1
All of the 0.5 showstoppers are out of the way and things are looking pretty solid. Shall we push out a release candidate? I propose the following tag and artifacts for 0.5.0-rc1 SVN Tag: https://svn.apache.org/repos/asf/incubator/cassandra/tags/cassandra-0.5.0-rc1 0.5.0-rc1 artifacts: http://people.apache.org/~eevans If it's not obvious, +1 from me. :) [1] https://svn.apache.org/repos/asf/incubator/cassandra/tags/cassandra-0.5.0-rc1/CHANGES.txt -- Eric Evans eev...@rackspace.com
[VOTE RESULT] was: release cassandra 0.5.0-beta2
On Thu, 2009-12-10 at 10:23 -0600, Eric Evans wrote: > The Cassandra community voted on and approved the release of Apache > Cassandra 0.5.0-beta2. We would now like to request the approval of the > Incubator PMC for this release. > > Cassandra is a massively scalable, eventually consistent, distributed, > structured key-value store. > > Podling vote thread: http://thread.gmane.org/gmane.comp.db.cassandra.devel/696 > 0.5.0-beta2 artifacts: http://people.apache.org/~eevans > SVN tag: > https://svn.apache.org/repos/asf/incubator/cassandra/tags/cassandra-0.5.0-beta2 > Project home: http://incubator.apache.org/cassandra/ > Incubation status: http://incubator.apache.org/projects/cassandra.html > > We received two binding votes[1][2] during the poddling vote, so we'll need 1 > more. Any help with reviewing/voting from outside our mentors list would be > appreciated. > > The vote will remain open for 72 hours (or longer if needed). The vote is now closed with the following tally: * +1 votes: 3 (Matthieu Riou[1], Ian Holsman[2], ant elder[3]) * 0 votes: 0 * -1 votes: 0 The vote passes. [1] http://article.gmane.org/gmane.comp.db.cassandra.devel/700 [2] http://article.gmane.org/gmane.comp.db.cassandra.devel/702 [3] http://www.mail-archive.com/gene...@incubator.apache.org/msg23530.html -- Eric Evans eev...@rackspace.com
[VOTE] release cassandra 0.5.0-beta2
The Cassandra community voted on and approved the release of Apache Cassandra 0.5.0-beta2. We would now like to request the approval of the Incubator PMC for this release. Cassandra is a massively scalable, eventually consistent, distributed, structured key-value store. Podling vote thread: http://thread.gmane.org/gmane.comp.db.cassandra.devel/696 0.5.0-beta2 artifacts: http://people.apache.org/~eevans SVN tag: https://svn.apache.org/repos/asf/incubator/cassandra/tags/cassandra-0.5.0-beta2 Project home: http://incubator.apache.org/cassandra/ Incubation status: http://incubator.apache.org/projects/cassandra.html We received two binding votes[1][2] during the poddling vote, so we'll need 1 more. Any help with reviewing/voting from outside our mentors list would be appreciated. The vote will remain open for 72 hours (or longer if needed). Regards, [1] http://article.gmane.org/gmane.comp.db.cassandra.devel/700 [2] http://article.gmane.org/gmane.comp.db.cassandra.devel/702 -- Eric Evans eev...@rackspace.com
[VOTE] Release 0.5.0-beta2
Since beta1 there have been known bugs fixed, new bugs discovered, and then fixed, optimizations made, and some nifty new enhancements (see CHANGES.txt[1]). Also, the for-0.5 list is getting quite short[2]. I propose the following tag and artifacts for 0.5.0-beta2 SVN Tag: https://svn.apache.org/repos/asf/incubator/cassandra/tags/cassandra-0.5.0-beta2 0.5.0-beta2 artifacts: http://people.apache.org/~eevans [1] https://svn.apache.org/repos/asf/incubator/cassandra/tags/cassandra-0.5.0-beta2/CHANGES.txt -- Eric Evans eev...@rackspace.com
Re: stress insert benchmark & cassandra hangup/crash
On Tue, 2009-12-01 at 15:25 +0200, pa...@kreado.com pop wrote:
> I did simple insert benchmark in java (see code below). It uses 5
> threads to write records in one CF.
> After some point cassandra hangup, then crashes. I use single node
> cassandra installation with commit log on separate hdd.
>
> Hardware:
> AMD Athlon(tm) 64 X2 Dual Core Processor 4200+
> 4 GB RAM,
> 2xHDD Samsung 1TB 32MB cache 7200RPM
[ ... ]
> After long pause cassandra crashes (i use 1GB for java heap):
>
> java.lang.OutOfMemoryError: Java heap space
> Dumping heap to java_pid21132.hprof ...
> Heap dump file created [1196864899 bytes in 51.159 secs]
>
> I tried this testcase on three mashines with latest development
> version
> of cassandra and with 0.4.2. And i got the same problems.
[ ... ]
> client.insert("suggy",
> String.valueOf(i),
> cp,
>
> "".getBytes("UTF-8"),
> timestamp,
> ConsistencyLevel.ZERO);
With ConsistencyLevel.ZERO writes are completely asynchronous, so one
possibility is that you are simply pushing more writes than the node can
handle and it's getting further and further behind, eventually
exhausting the heap.
You should probably also read
http://wiki.apache.org/cassandra/MemtableThresholds if you haven't
already.
--
Eric Evans
eev...@rackspace.com
Re: build fails with "ant clean gen-thrift-java build"
On Tue, 2009-12-01 at 11:36 -0600, Ted Zlatanov wrote: > I am getting this error with a fresh SVN checkout (but not if I just do > a build). Am I missing something? Reading the Ant build.xml didn't > help, I don't see a better way to generate the bindings. I thought it > was my auth work but this happens from SVN as well (I need to regenerate > the Thrift bindings because I provide extra methods and exceptions). > > Sorry if this is an obvious thing, it's my first time using Thrift... > > Thanks > Ted > > > ant clean gen-thrift-java build > > Buildfile: build.xml > > clean: >[delete] Deleting directory /home/tzz/source/cassandra-trunk/build >[delete] Deleting directory /home/tzz/source/cassandra-trunk/src/gen-java > > gen-thrift-java: > [echo] Generating Thrift Java code from > /home/tzz/source/cassandra-trunk/interface/cassandra.thrift > > build-subprojects: > > init: > [mkdir] Created dir: /home/tzz/source/cassandra-trunk/build/classes > [mkdir] Created dir: /home/tzz/source/cassandra-trunk/build/test/classes > [mkdir] Created dir: /home/tzz/source/cassandra-trunk/src/gen-java > > check-gen-cli-grammar: > > gen-cli-grammar: > [echo] Building Grammar > /home/tzz/source/cassandra-trunk/src/java/org/apache/cassandra/cli/Cli.g > > build-project: > [ ... ] When/where did your thrift come from? I'm guessing this is either a recent regression there, or that you're using a version that is too old. FWIW, r808609 seems OK. -- Eric Evans eev...@rackspace.com
[VOTE RESULTS] was: release cassandra 0.5.0-beta1
On Mon, 2009-11-23 at 12:40 -0600, Eric Evans wrote: > The Cassandra community voted on and approved the release of Apache > Cassandra 0.5.0-beta1. We would now like to request the approval of the > Incubator PMC for this release. > > Cassandra is a massively scalable, eventually consistent, distributed, > structured key-value store. > > Podling vote thread: > http://thread.gmane.org/gmane.comp.db.cassandra.devel/586 > 0.5.0-beta1 artifacts: http://people.apache.org/~eevans > SVN tag: > https://svn.apache.org/repos/asf/incubator/cassandra/tags/cassandra-0.5.0-beta1 > Project home: http://incubator.apache.org/cassandra/ > Incubation status: http://incubator.apache.org/projects/cassandra.html > > We received one binding vote during the poddling vote, so we'll need 2 > more. Any help with reviewing/voting from outside our mentors list would > be appreciated. > > The vote will remain open for 72 hours (or longer if needed). The vote is now closed with the following tally: * +1 votes: 3 (Ian Holsman, ant elder, Alan D. Cabrera) * 0 votes: 0 * -1 votes: 0 The vote passes. Many thanks to those that took time to review the release and vote, it's appreciated! -- Eric Evans eev...@rackspace.com
[VOTE] release cassandra 0.5.0-beta1
The Cassandra community voted on and approved the release of Apache Cassandra 0.5.0-beta1. We would now like to request the approval of the Incubator PMC for this release. Cassandra is a massively scalable, eventually consistent, distributed, structured key-value store. Podling vote thread: http://thread.gmane.org/gmane.comp.db.cassandra.devel/586 0.5.0-beta1 artifacts: http://people.apache.org/~eevans SVN tag: https://svn.apache.org/repos/asf/incubator/cassandra/tags/cassandra-0.5.0-beta1 Project home: http://incubator.apache.org/cassandra/ Incubation status: http://incubator.apache.org/projects/cassandra.html We received one binding vote during the poddling vote, so we'll need 2 more. Any help with reviewing/voting from outside our mentors list would be appreciated. The vote will remain open for 72 hours (or longer if needed). Regards, -- Eric Evans eev...@rackspace.com
Re: [VOTE] Release 0.5.0-beta1
On Mon, 2009-11-23 at 22:45 +0900, Jaakko wrote: > > We can still incorporate changes before the final release, I > wouldn't > > consider this a hard-freeze yet (in fact, you'll notice that I > tagged > > from trunk; no 0.5 branch has been created yet). > > Well, now it is Monday :-) I think if we can include #575 (or similar > fix), bootstrapping should be OK for beta, so +1 from me too :-) The way a release works for incubator projects is that we first vote amongst ourselves, and then turn it over to a vote on the IPMC list (which lasts a minimum of 72 hours). So, incorporating #575 into beta1 would be mean resetting the time-line. We'll get this fix into the next beta which should will be along Real Soon Now. -- Eric Evans eev...@rackspace.com
Re: Graduation?
On Fri, 2009-11-20 at 13:09 +, ant elder wrote: > > That being said, I don't think anyone in the "should be frowned > > upon" camp were swayed, and we have to do what the IPMC tells us > > to (if we want to graduate), so what choice do we have? > > The IPMC doesn't like telling poddlings what to do, they like them to > work things out for themselves. I understand what you're saying, and I honestly believe that the structure put in place and the the people involved are well-meaning, but the simple fact of that matter is that the IPMC is in a position of power over this project. > The question was asked and people gave they views, and some sounded > like strongly held views. No one said they would -1 a graduation vote > but that may just be because thats not what the question on general@ > asked. You could ask that specific question, or you could just hold a > graduation vote to see. Or you could first try to appease those not in > favour of RTC by trying to make some changes ... and say that we worked it out for ourselves? :) > - could CTR be tried for a while to see how it goes? Or try CTR for > just non-critical bits of code, or only for smaller changes? Maybe it > will work now, but if it doesn't you can at least then say look we > tried but it doesn't work for this project. We are using CTR for minor non-intrusive changes, build, scripts, documentation, etc. -- Eric Evans eev...@rackspace.com
Re: [VOTE] Release 0.5.0-beta1
On Fri, 2009-11-20 at 11:14 +0900, Jaakko wrote: > I'd propose to wait for a short while (until Monday or so). I think > there are some issues with bootstrapping (discussed with Jonathan > yesterday) and some of the things in CHANGES.txt are currently not > true. I'm working on bootstrap/move issues currently, so I'd propose > to wait to fix most obvious of them before giving trunk any "official" > beta status. We can still incorporate changes before the final release, I wouldn't consider this a hard-freeze yet (in fact, you'll notice that I tagged from trunk; no 0.5 branch has been created yet). > Also, it would be nice to have proactive repair in as well. I agree, but there are always items like this. I'd personally rather err on the side of Release Early, Release Often, then to get caught up hanging on a bit more for the Next Cool Thing. -- Eric Evans eev...@rackspace.com
Re: [VOTE] Release 0.5.0-beta1
On Thu, 2009-11-19 at 19:59 -0600, Eric Evans wrote: > We've just about worked our way through the list of 0.5.0 blockers and > it would be great to get some of this new hotness into the hands of our > users, so... > > I propose the following tag and artifacts for 0.5.0-beta1 > > SVN Tag: > https://svn.apache.org/repos/asf/incubator/cassandra/tags/cassandra-0.5.0-beta1 > 0.5.0-beta1 artifacts: http://people.apache.org/~eevans > > [1] > https://svn.apache.org/repos/asf/incubator/cassandra/tags/cassandra-0.5.0-beta1/CHANGES.txt +1 :) -- Eric Evans eev...@rackspace.com
[VOTE] Release 0.5.0-beta1
We've just about worked our way through the list of 0.5.0 blockers and it would be great to get some of this new hotness into the hands of our users, so... I propose the following tag and artifacts for 0.5.0-beta1 SVN Tag: https://svn.apache.org/repos/asf/incubator/cassandra/tags/cassandra-0.5.0-beta1 0.5.0-beta1 artifacts: http://people.apache.org/~eevans [1] https://svn.apache.org/repos/asf/incubator/cassandra/tags/cassandra-0.5.0-beta1/CHANGES.txt -- Eric Evans eev...@rackspace.com
Re: Graduation?
On Wed, 2009-11-18 at 22:26 +, ant elder wrote: > Looking at whats been said its quite evenly split with about half > saying RTC could be ok and half suggesting RTC should be frowned upon. > So what to do? Optimistically push on with graduation and hope people > don't vote against it due to this? Modify the current commit process > somehow? I didn't think that anyone was able to demonstrate an actual problem. There was plenty of discussion about why it's bad, past experiences, etc, but no one was able to point at something specific and say, "See, this right here is indicative of the shortcomings of your workflow". That being said, I don't think anyone in the "should be frowned upon" camp were swayed, and we have to do what the IPMC tells us to (if we want to graduate), so what choice do we have? -- Eric Evans eev...@rackspace.com
Re: [VOTE] Website
On Thu, 2009-11-12 at 18:36 -0800, Paul Querna wrote: > > The new site is live. Let me know if you spot any problems (or > > better yet, submit a ticket :)). > > > > Thanks! > > the incubator logo in the footer 404s: > http://incubator.apache.org/cassandra/media/images/apache-incubator-small.png This should be good now. -- Eric Evans eev...@rackspace.com
Re: [VOTE] Website
On Wed, 2009-11-11 at 16:10 -0600, Eric Evans wrote: > The current website is quite ugly, and I don't know about you, but I'm > itching to put the new project logo to use, so I'd like to propose > publishing http://cassandra.deadcafe.org (to > http://incubator.apache.org/cassandra). The new site is live. Let me know if you spot any problems (or better yet, submit a ticket :)). Thanks! -- Eric Evans eev...@rackspace.com
[VOTE] Website
The current website is quite ugly, and I don't know about you, but I'm itching to put the new project logo to use, so I'd like to propose publishing http://cassandra.deadcafe.org (to http://incubator.apache.org/cassandra). This is a slightly tweaked version of Daniel Lundin's work from CASSANDRA-231[1] (thanks Daniel!), and the content is nearly identical to what is on the current site. I do not consider this to be the final word on the matter, I think there is still much to be done. For example, the logo w/text is something I cobbled together in Gimp and should be considered a placeholder. Still, it's much better than what we currently have and we can incrementally improve it as we go forward. [1] https://issues.apache.org/jira/browse/CASSANDRA-231 -- Eric Evans eev...@rackspace.com
Re: Atlassian JIRA
On Tue, 2009-11-10 at 10:55 +1100, Kevin Williams wrote: > Just a small typo one of our developers noticed on your cassandra > homepage <http://incubator.apache.org/cassandra/> . You refer to > "Apache JIRA" when you either mean "Apache's instance of JIRA" or > "Atlassian JIRA." If you could change it, Atlassian would be > appreciative. This has been fixed in SVN and should appear on the live site when the next sync occurs (within the hour). Thanks for pointing this out Kevin. -- Eric Evans eev...@rackspace.com
[VOTE RESULTS] was: [VOTE] Release cassandra 0.4.2
On Fri, 2009-11-06 at 11:37 -0600, Eric Evans wrote: > The Cassandra community voted on and approved the release of Apache > Cassandra 0.4.2. We would now like to request the approval of the > Incubator PMC for this release. > > Cassandra is a massively scalable, eventually consistent, distributed, > structured key-value store. > > Podling vote thread: > http://www.mail-archive.com/cassandra-dev@incubator.apache.org/msg01036.html > 0.4.2 artifacts: http://people.apache.org/~eevans > SVN tag: > https://svn.apache.org/repos/asf/incubator/cassandra/tags/cassandra-0.4.2 > Project home: http://incubator.apache.org/cassandra/ > Incubation status: http://incubator.apache.org/projects/cassandra.html > > Note: We've already received two binding +1s during the poddling release > vote[1][2]. > > The vote will remain open for 72 hours (or longer if needed). > > Regards, > > [1] http://article.gmane.org/gmane.comp.db.cassandra.devel/505 > [2] http://article.gmane.org/gmane.comp.db.cassandra.devel/501 The vote is now closed with the following tally: * +1 votes: 3 (Matthieu Riou, ant elder, Leo Simons) * 0 votes: 0 * -1 votes: 0 The vote passes. Thanks! -- Eric Evans eev...@rackspace.com
Re: Graduation?
On Fri, 2009-11-06 at 11:21 +, ant elder wrote: > > Can someone explain how this RTC mode is actually working right now, > what is the process for reviewing, voting, and applying the changes? In a practice: 1. Folks attach patches to Jira issues, (committers too). 2. Someone (anyone really) gives it at least a once over and ... 2a. +1s the change 2b. provides feedback, (goto #1) 3. A committer commits the patch Typically, when a change is controversial, invasive, or just touches a particularly tricky part of the code-base, then more people take notice and look it over with a greater degree of scrutiny; most of the time though it's just a quick sanity check, making sure it builds, passes/includes tests, etc. We've pretty much pulled the trigger (often within minutes), after the very first +1 and then rolled it back and/or fixed it if someone points out a problem after the fact. I'm personally not a big fan of RTC in general, but if I'm honest, it has been working pretty well in practice thus far; there are other aspects of our work-flow that offend my sensibilities worse than this. :) -- Eric Evans eev...@rackspace.com
Re: Graduation?
On Thu, 2009-11-05 at 17:04 -0600, Michael Greene wrote: > It was previously proposed that documentation be CTR. I would be in > favor of this, and extending it to include scripts, licensing, and > other project management materials. I would be in favor of relaxing the RTC "requirement" to be more of an "understanding", and letting common sense prevail (for as long as that doesn't prove to be a problem anyway :)). Because yes, there is a big difference between wanting to have another set of eyes on a huge re-factoring of a critical subsystem, and correcting spelling errors in a README. -- Eric Evans eev...@rackspace.com
Re: [VOTE] Release 0.4.2
On Wed, 2009-11-04 at 15:32 -0600, Eric Evans wrote: > The 0.4 branch has received a number of important bug fixes[1] since our > last point release (0.4.1), plus, things went so smoothly last time that > I can't pass up the opportunity to try my luck at a release during > ApacheCon. :) > > I propose the following tag and artifacts for release as 0.4.2. > > SVN Tag: > https://svn.apache.org/repos/asf/incubator/cassandra/tags/cassandra-0.4.2 > 0.4.2 artifacts: http://people.apache.org/~eevans +1 -- Eric Evans eev...@rackspace.com
[VOTE] Release 0.4.2
The 0.4 branch has received a number of important bug fixes[1] since our last point release (0.4.1), plus, things went so smoothly last time that I can't pass up the opportunity to try my luck at a release during ApacheCon. :) I propose the following tag and artifacts for release as 0.4.2. SVN Tag: https://svn.apache.org/repos/asf/incubator/cassandra/tags/cassandra-0.4.2 0.4.2 artifacts: http://people.apache.org/~eevans [1] https://svn.apache.org/repos/asf/incubator/cassandra/tags/cassandra-0.4.2/CHANGES.txt -- Eric Evans eev...@rackspace.com
Re: ApacheCon2009
On Wed, 2009-10-07 at 12:05 -0500, Eric Evans wrote: > ApacheCon is next month (November 2-6), I'll be there, how many others > are planning to attend? Is there any interest in organizing a meetup/bug > squashing party/hack-a-thon that week? Any takers? I'm in Oakland all week, and at the very least it'd be great to meet up with folks for beers and/or dinner. -- Eric Evans eev...@rackspace.com
Apt repository move
Just a heads up: The debian packaging repository has moved; if you install from package you'll need to update sources.list to: deb http://www.apache.org/dist/incubator/cassandra/debian unstable main deb-src http://www.apache.org/dist/incubator/cassandra/debian unstable main Sorry for the inconvenience. -- Eric Evans eev...@rackspace.com
[VOTE RESULTS] was: [VOTE] Release cassandra 0.4.1
The vote is now closed with the following tally: * +1 votes: 5 (Paul Querna, Ian Holsman, Matthieu Riou, Niall Pemberton, and ant elder) * 0 votes: 0 * -1 votes: 0 The vote passes. Thanks! On Tue, 2009-10-13 at 10:12 -0500, Eric Evans wrote: > The Cassandra community voted on and approved the release of Apache > Cassandra 0.4.1. We would now like to request the approval of the > Incubator PMC for this release. > > Cassandra is a massively scalable, eventually consistent, distributed, > structured key-value store. > > Podling vote thread: > http://www.mail-archive.com/cassandra-dev@incubator.apache.org/msg00987.html > 0.4.1 artifacts: http://people.apache.org/~eevans > SVN tag: > https://svn.apache.org/repos/asf/incubator/cassandra/tags/cassandra-0.4.1 > Project home: http://incubator.apache.org/cassandra/ > Incubation status: http://incubator.apache.org/projects/cassandra.html > > Note: We've already received 3 binding +1s during the podding release > vote[0][1][2]. > > The vote will remain open for 72 hours. > > Thank you for your time. > > Regards, > > [0] > http://www.mail-archive.com/cassandra-dev@incubator.apache.org/msg00995.html > [1] > http://www.mail-archive.com/cassandra-dev@incubator.apache.org/msg00994.html > [2] > http://www.mail-archive.com/cassandra-dev@incubator.apache.org/msg00996.html -- Eric Evans eev...@rackspace.com
Re: [VOTE] Release cassandra 0.4.1
On Tue, 2009-10-13 at 16:48 +0100, Niall Pemberton wrote: > * Could you put the artefacts for each release in a separate directory > next time, just to make it completely obvious whats being voted on. Sure, no problem. > * The pom.xml shipped in the source distro is out of sync with the > build.xml and doesn't work This is sort of a known issue[0]; we'll get it taken care of (or have it removed). Thanks Niall. [0] https://issues.apache.org/jira/browse/CASSANDRA-430 -- Eric Evans eev...@rackspace.com
[VOTE] Release cassandra 0.4.1
The Cassandra community voted on and approved the release of Apache Cassandra 0.4.1. We would now like to request the approval of the Incubator PMC for this release. Cassandra is a massively scalable, eventually consistent, distributed, structured key-value store. Podling vote thread: http://www.mail-archive.com/cassandra-dev@incubator.apache.org/msg00987.html 0.4.1 artifacts: http://people.apache.org/~eevans SVN tag: https://svn.apache.org/repos/asf/incubator/cassandra/tags/cassandra-0.4.1 Project home: http://incubator.apache.org/cassandra/ Incubation status: http://incubator.apache.org/projects/cassandra.html Note: We've already received 3 binding +1s during the podding release vote[0][1][2]. The vote will remain open for 72 hours. Thank you for your time. Regards, [0] http://www.mail-archive.com/cassandra-dev@incubator.apache.org/msg00995.html [1] http://www.mail-archive.com/cassandra-dev@incubator.apache.org/msg00994.html [2] http://www.mail-archive.com/cassandra-dev@incubator.apache.org/msg00996.html -- Eric Evans eev...@rackspace.com
Re: [RE-VOTE] Release 0.4.1
On Mon, 2009-10-12 at 14:32 -0500, Eric Evans wrote: > Ok, sorry for the false start, here it is again (as r824462). > > The 0.4 branch has received a number of important bug fixes[1] since > we > released 0.4.0, it feels about time for an 0.4.1. > > Shall we? :) +1 -- Eric Evans eev...@rackspace.com
[RE-VOTE] Release 0.4.1
Ok, sorry for the false start, here it is again (as r824462). The 0.4 branch has received a number of important bug fixes[1] since we released 0.4.0, it feels about time for an 0.4.1. Shall we? :) SVN Tag: https://svn.apache.org/repos/asf/incubator/cassandra/tags/cassandra-0.4.1 0.4.1 artifacts: http://people.apache.org/~eevans [1] https://svn.apache.org/repos/asf/incubator/cassandra/tags/cassandra-0.4.1/CHANGES.txt -- Eric Evans eev...@rackspace.com
[CANCELLED][VOTE] Release 0.4.1
On Mon, 2009-10-12 at 13:45 -0500, Eric Evans wrote: > > The 0.4 branch has received a number of important bug fixes[1] since > we > released 0.4.0, it feels about time for an 0.4.1. > > Shall we? :) > > SVN Tag: > https://svn.apache.org/repos/asf/incubator/cassandra/tags/cassandra-0.4.1 > 0.4.1 artifacts: http://people.apache.org/~eevans Doh! Hold off for just a bit please. Jonathan just checked in a fix for CASSANDRA-478 and it'd be a shame to not have that make 0.4.1. I'll restart the vote momentarily. -- Eric Evans eev...@rackspace.com
[VOTE] Release 0.4.1
The 0.4 branch has received a number of important bug fixes[1] since we released 0.4.0, it feels about time for an 0.4.1. Shall we? :) SVN Tag: https://svn.apache.org/repos/asf/incubator/cassandra/tags/cassandra-0.4.1 0.4.1 artifacts: http://people.apache.org/~eevans [1] https://svn.apache.org/repos/asf/incubator/cassandra/tags/cassandra-0.4.1/CHANGES.txt -- Eric Evans eev...@rackspace.com
Re: [CLOSED][VOTE] Project Logo
On Fri, 2009-10-09 at 01:49 -0500, Denny Abraham wrote: > I'm confused, isn't that four logos? It's one logo shown in color and greyscale (for printing, etc), shown on both light and dark backgrounds. -- Eric Evans eev...@rackspace.com
[CLOSED][VOTE] Project Logo
The voting period is now up and the detailed results can be found below, but for those that would rather cut to the chase, the winning logo is: http://99designs.com/contests/28940/entries/598 OpenSTV version 1.5 (http://www.OpenSTV.org/) Loading ballots from file ballots.txt. Ballot file contains 13 candidates and 32 ballots. No candidates have withdrawn. Ballot file contains 32 non-empty ballots. Counting votes for Ballot data from file ballots.txt using Condorcet Voting. 13 candidates running for 1 seat. Using Schwartz Sequential Dropping for the completion method. Pairwise Comparison Matrix: | 30| 33| 598| 369| 576| 2|NOTA| 32| 90| 175| 173| 478| 291 +++++++++++++ 30| 0| 12| 8| 11| 17| 16| 23| 13| 11| 12| 11| 13| 12 33| 19| 0| 15| 17| 21| 18| 29| 18| 13| 18| 18| 22| 19 598| 16| 15| 0| 11| 18| 16| 21| 15| 14| 15| 14| 17| 13 369| 14| 14| 13| 0| 21| 14| 23| 15| 14| 16| 14| 16| 14 576| 8| 9| 5| 4| 0| 9| 22| 6| 7| 8| 8| 6| 7 2| 7| 13| 7| 10| 15| 0| 22| 11| 11| 11| 10| 13| 12 NOTA| 1| 1| 1| 1| 1| 1| 0| 1| 1| 1| 1| 1| 1 32| 13| 13| 11| 13| 20| 15| 25| 0| 11| 15| 15| 17| 16 90| 17| 17| 13| 15| 20| 17| 26| 17| 0| 20| 18| 19| 15 175| 14| 12| 9| 10| 16| 14| 23| 11| 7| 0| 11| 15| 11 173| 14| 12| 10| 12| 16| 15| 23| 11| 9| 14| 0| 12| 13 478| 11| 8| 6| 8| 18| 10| 22| 10| 8| 10| 13| 0| 8 291| 13| 11| 10| 10| 17| 12| 22| 11| 13| 14| 12| 16| 0 Smith Set: 33, 598, 369, and 90 Using Schwartz sequential dropping to choose the winner. Matrix of beatpath magnitudes: | 30| 33| 598| 369| 576| 2|NOTA| 32| 90| 175| 173| 478| 291 +++++++++++++ 30| 13| 0| 0| 0| 17| 16| 23| 0| 0| 13| 13| 13| 13 33| 19| 13| 13| 17| 21| 18| 29| 18| 13| 18| 18| 22| 19 598| 16| 14| 13| 14| 18| 16| 21| 15| 14| 15| 15| 17| 15 369| 14| 13| 13| 13| 21| 15| 23| 15| 13| 16| 15| 16| 15 576| 0| 0| 0| 0| 0| 0| 22| 0| 0| 0| 0| 0| 0 2| 13| 0| 0| 0| 15| 13| 22| 0| 0| 13| 13| 13| 13 NOTA| 0| 0| 0| 0| 0| 0| 0| 0| 0| 0| 0| 0| 0 32| 14| 0| 0| 0| 20| 15| 25| 0| 0| 15| 15| 17| 16 90| 17| 17| 13| 17| 20| 17| 26| 17| 13| 20| 18| 19| 17 175| 14| 0| 0| 0| 16| 14| 23| 0| 0| 13| 13| 15| 13 173| 14| 0| 0| 0| 16| 15| 23| 0| 0| 14| 13| 14| 13 478| 13| 0| 0| 0| 18| 13| 22| 0| 0| 13| 13| 13| 13 291| 14| 0| 0| 0| 17| 14| 22| 0| 0| 14| 13| 16| 13 Winner is 598. -- Eric Evans eev...@rackspace.com <> OPENSTV_DIR = OpenSTV-1.5 all: ballots.txt: sed -s "s/ # .\+//g" ballots.raw > ballots.txt calculate: ballots.txt cd $(OPENSTV_DIR) && ./runElection.py Condorcet ../ballots.txt clean: rm -f ballots.txt
Re: Problems starting cassandra - Please help
On Thu, 2009-10-08 at 09:37 +0530, Shreya Chakravarty wrote: > > I am facing issues starting Cassandra > > euca-linux-sles:/opt/cassandra/bin # Error: Exception thrown by the > agent : java.net.MalformedURLException: Local host name unknown: > java.net.UnknownHostException: euca-linux-sles: euca-linux-sles Does the local host name, euca-linux-sles, resolve, either through DNS or /etc/hosts? -- Eric Evans eev...@rackspace.com
ApacheCon2009
ApacheCon is next month (November 2-6), I'll be there, how many others are planning to attend? Is there any interest in organizing a meetup/bug squashing party/hack-a-thon that week? -- Eric Evans eev...@rackspace.com
Re: [VOTE] Project Logo
On Mon, 2009-10-05 at 10:12 -0500, Eric Evans wrote:
> ~~{ Ballot }~~
> [ 1] 2http://99designs.com/contests/28940/entries/002
> [ 2] 30 http://99designs.com/contests/28940/entries/030
> [ 3] 32 http://99designs.com/contests/28940/entries/032
> [10] 33 http://99designs.com/contests/28940/entries/033
> [11] 90 http://99designs.com/contests/28940/entries/090
> [12] 173 http://99designs.com/contests/28940/entries/173
> [ 6] 175 http://99designs.com/contests/28940/entries/175
> [ 9] 291 http://99designs.com/contests/28940/entries/291
> [ 4] 369 http://99designs.com/contests/28940/entries/369
> [ 7] 478 http://99designs.com/contests/28940/entries/478
> [ 8] 576 http://99designs.com/contests/28940/entries/576
> [ 5] 598 http://99designs.com/contests/28940/entries/598
> [13] NOTA
> ~~{ Ballot }~~
--
Eric Evans
eev...@rackspace.com
[VOTE] Project Logo
Alrighty then. Time to vote on a project logo.
The ballot is made up of all the finalist logos with a rating of either
4 or 5 stars[0], and "None of the Above" (just in case you want to
express your disgust with one or more of the choices).
To vote, reply to the list and fill in the boxes of the ballot below.
Rank each choice with a number between 1 and 13 (where 1 is your most
favorite, and 13 is your least). It is not strictly necessary to rank
every choice (though it is recommended). Skipping numbers is also OK,
but it has no bearing on the weight of your rankings, (i.e. 2,5,10 is
the equivalent of 1,2,3).
~~{ Ballot }~~
[ ] 2http://99designs.com/contests/28940/entries/002
[ ] 30 http://99designs.com/contests/28940/entries/030
[ ] 32 http://99designs.com/contests/28940/entries/032
[ ] 33 http://99designs.com/contests/28940/entries/033
[ ] 90 http://99designs.com/contests/28940/entries/090
[ ] 173 http://99designs.com/contests/28940/entries/173
[ ] 175 http://99designs.com/contests/28940/entries/175
[ ] 291 http://99designs.com/contests/28940/entries/291
[ ] 369 http://99designs.com/contests/28940/entries/369
[ ] 478 http://99designs.com/contests/28940/entries/478
[ ] 576 http://99designs.com/contests/28940/entries/576
[ ] 598 http://99designs.com/contests/28940/entries/598
[ ] NOTA
~~{ Ballot }~~
The vote will remain open until Thursday at 22:00 UTC. I will collect
the votes from the list and use OpenSTV's condorcet method to calculate
the pairwise rankings and announce a winner (no later than Friday
morning).
May the best logo win!
[0]
http://99designs.com/contests/28940?orderby=timesubmitted&filterby=highrating
[1] http://www.openstv.org
--
Eric Evans
eev...@rackspace.com
Re: Logo Design Contest
On Wed, 2009-09-30 at 16:13 -0500, Eric Evans wrote: > On Wed, 2009-09-23 at 11:39 -0500, Eric Evans wrote: > > A logo design contest is now underway at 99designs.com. > > > > http://99designs.com/contests/28940 > > > > The contest brief can be found here: > > http://99designs.com/contests/28940/brief. If you're worried that it's > > missing something critical (or includes something it shouldn't), leave a > > comment on the contest page and/or let me know right away. > > The submission part of the 99designs.com contest is now over; we ended > up with a whopping 618 submissions (yikes). Now comes the hard part, > picking a winner. :) > > Fortunately, a number of people have been following the contest and > providing feedback in the comments area or in #cassandra, and as a > result we've got the list weeded down to the best 48 designs[0]. > However, since it's probably not practical to run a vote with more than > say 10 or 15 options, the final ballot will likely be limited to those > entries rated 4 or 5 stars[1]. > > I'll wait a few days before starting up a vote to give everyone a chance > to weigh-in on what should make the final ballot. Your opinion matters, > so take a look at the contest page and either send me your suggestions, > or bring them up here on the list. Does this mean that everyone is happy with the 11 candidate logos? http://99designs.com/contests/28940?orderby=timesubmitted&filterby=highrating We'll need to start a vote soon (there are time limits imposed by 99designs for awarding the payout). -- Eric Evans eev...@rackspace.com
Re: Logo Design Contest
On Wed, 2009-09-23 at 11:39 -0500, Eric Evans wrote: > A logo design contest is now underway at 99designs.com. > > http://99designs.com/contests/28940 > > The contest brief can be found here: > http://99designs.com/contests/28940/brief. If you're worried that it's > missing something critical (or includes something it shouldn't), leave a > comment on the contest page and/or let me know right away. The submission part of the 99designs.com contest is now over; we ended up with a whopping 618 submissions (yikes). Now comes the hard part, picking a winner. :) Fortunately, a number of people have been following the contest and providing feedback in the comments area or in #cassandra, and as a result we've got the list weeded down to the best 48 designs[0]. However, since it's probably not practical to run a vote with more than say 10 or 15 options, the final ballot will likely be limited to those entries rated 4 or 5 stars[1]. I'll wait a few days before starting up a vote to give everyone a chance to weigh-in on what should make the final ballot. Your opinion matters, so take a look at the contest page and either send me your suggestions, or bring them up here on the list. Thanks, [0] http://99designs.com/contests/28940?orderby=timesubmitted&filterby=noteliminated [1] http://99designs.com/contests/28940?orderby=timesubmitted&filterby=highrating -- Eric Evans eev...@rackspace.com
Re: Multi-node emulator?
On Tue, 2009-09-29 at 20:56 -0700, Ryan Cunningham wrote: > As part of some internal Cassandra development we were doing, we developed > code that wraps Cassandra, sets up and launches multiple Cassandra instances > on the local machine (using virtual ips), and executes test cases to validate > read repair, node failure and recovery, message delay recovery and a few > other multinode test cases. We want to contribute this code back, but we do > not have anyone that can stay on for maintenance and further development as > the project has shifted away from Cassandra for now. Is this group interested > in furthering the work, or at least taking a look? Absolutely. Is this something that you can post as files or patches to a Jira ticket (https://issues.apache.org/jira/browse/CASSANDRA)? -- Eric Evans eev...@rackspace.com
Announcement: 0.4.0
Ladies and gentlemen, I give you Cassandra 0.4.0. It's hard to imagine that it has only been 2 months since our very first release[1]; an impressive amount of progress has been made. For example: * Nodes can now scale to billions of keys instead of millions. * There is support for multiple keyspaces (formerly known as tables). * You can now create snapshots * A new bootstrap feature for adding nodes to a running cluster * A new multiget API * Numerous improvements to the Thrift API And many, many, more. In fact, don't take my word for it, check out the changelog[2], or the 176 closed Jira issues (176!)[3]. Many thanks to all those that contributed patches, reviewed, tested, documented, or counseled. [1] http://www.mail-archive.com/cassandra-u...@incubator.apache.org/msg00289.html [2] https://svn.apache.org/repos/asf/incubator/cassandra/tags/cassandra-0.4.0-final/CHANGES.txt [3] https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&&pid=12310865&fixfor=12313862&resolution=1&sorter/field=issuekey&sorter/order=DESC -- Eric Evans eev...@rackspace.com
[RESULT][VOTE] Release cassandra 0.4.0 (final)
The vote is now close with the following votes cast. +1 votes: 3 (Paul Querna[1], Matthieu Riou[2], and Ian Holsman) 0 votes: 0 -1 votes: 0 The vote passes. [1] http://www.mail-archive.com/cassandra-dev@incubator.apache.org/msg00918.html [2] http://www.mail-archive.com/cassandra-dev@incubator.apache.org/msg00917.html -- Eric Evans eev...@rackspace.com
Re: Your Feedback Needed (was: Logo Design Contest)
On Thu, 2009-09-24 at 15:29 -0700, Sal Fuentes wrote: > Would it not be fair to somehow include the existing logo designs > in http://issues.apache.org/jira/browse/CASSANDRA-231 ? Yes, it would, and I left a comment to that effect[1] earlier today. [1] http://issues.apache.org/jira/browse/CASSANDRA-231?focusedCommentId=12759241&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#action_12759241 -- Eric Evans eev...@rackspace.com
Your Feedback Needed (was: Logo Design Contest)
We're one day into the 99designs.com logo contest and there are already some interesting proposals (8 as of this moment). Feedback on the designs is an important part of this process though so please don't wait until the last minute, head over to http://99designs.com/contests/28940, have a look at the submissions, and leave some comments. Thanks! -- Eric Evans eev...@rackspace.com
Logo Design Contest
A logo design contest is now underway at 99designs.com. http://99designs.com/contests/28940 The contest brief can be found here: http://99designs.com/contests/28940/brief. If you're worried that it's missing something critical (or includes something it shouldn't), leave a comment on the contest page and/or let me know right away. I encourage everyone to bookmark the page, to check it frequently, and be sure to leave plenty of feedback as designs are submitted! Thanks, -- Eric Evans eev...@rackspace.com
Re: Debian apt repo
On Tue, 2009-09-22 at 09:48 +0200, Marcus Better wrote: > Any plan for getting this into Debian proper? Eventually, sure. > Is it too early? Yes, I think so. > If some minor cleanup is needed, I might be able to help. The first order of business will be to make sure that all of the dependencies are packaged, and of those, thrift is the biggest undertaking. I've filed an ITP[0] for that, and made some progress[1], but there is still much to do. Help is appreciated. [0] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=524135 [1] http://git.debian.org/?p=users/eevans/thrift.git -- Eric Evans eev...@rackspace.com
Debian apt repo
The Debian package repo is moving. The new sources are: deb http://www.apache.org/dist/incubator/cassandra/debian cassandra/ deb-src http://www.apache.org/dist/incubator/cassandra/debian cassandra/ The repo on people.apache.org/~eevans still works and will continue to for a week or so to give everyone a little time. Sorry for the inconvenience; let me know if you encounter any problems. -- Eric Evans eev...@rackspace.com
[VOTE] Release cassandra 0.4.0 (final)
The Cassandra community voted on and approved the release of Apache Cassandra 0.4.0. We would now like to request the approval of the Incubator PMC for this release. Cassandra is a massively scalable, eventually consistent, distributed, structured key-value store. Podling vote thread: http://www.mail-archive.com/cassandra-dev@incubator.apache.org/msg00908.html 0.4.0 artifacts: http://people.apache.org/~eevans SVN tag: https://svn.apache.org/repos/asf/incubator/cassandra/tags/cassandra-0.4.0-final Project home: http://incubator.apache.org/cassandra/ Incubation status: http://incubator.apache.org/projects/cassandra.html The differences between this and the recently approved RC2 are minor; it contains one bug fix (CASSANDRA-440), and a few documentation updates. If approved, this will be our new stable release, the default for new users, and one demonstrating significant progress over the current stable (0.3.0). We've already received 2 binding +1s during the poddling release vote[0][1], so we need at least one more (and no dissents obviously). The vote will remain open for 72 hours (or longer if needed). Thank you for your time. Regards, [0] http://www.mail-archive.com/cassandra-dev@incubator.apache.org/msg00917.html [1] http://www.mail-archive.com/cassandra-dev@incubator.apache.org/msg00918.html -- Eric Evans eev...@rackspace.com
[VOTE RESULT] was: [VOTE] 0.4.0 Final
On Fri, 2009-09-18 at 12:15 -0500, Eric Evans wrote: > It's been a little over a week since we voted on RC2 here > (http://www.mail-archive.com/cassandra-dev@incubator.apache.org/msg00887.html), > and no show stoppers have cropped up. I propose we release as final what is > currently in the cassandra-0.4 branch (r816701). The differences between rc2 > are quite minimal and include the fix for CASSANDRA-440, some changes under > contrib/, and an updated README.txt and CHANGES.txt. > > What say you? The vote passes; I'm going to move this over to gene...@incubator now to make it official. We already have two binding IPMC votes (pquerna and mriou), if at least one of the other mentors could cast a vote on gene...@incubator, it'd be highly appreciated. -- Eric Evans eev...@rackspace.com
Re: [PROPOSAL] CTR for all non-code changes
On Fri, 2009-09-18 at 13:12 -0700, Paul Querna wrote: > I am starting to believe it would be helpful if Cassandra adopted a > similar CTR policy for non-code changes on trunk and all branches. Works for me. -- Eric Evans eev...@rackspace.com
Re: [VOTE] 0.4.0 Final
On Fri, 2009-09-18 at 13:20 -0700, Matthieu Riou wrote: > You sure like throwing release votes on Fridays ;) Yeah, I was just thinking about that earlier. I swear that is unintentional. :) If it helps, I wasn't planning on taking it to gene...@incubator until after the weekend! P.S. Thanks for the vote btw. -- Eric Evans eev...@rackspace.com
Re: [VOTE] 0.4.0 Final
On Fri, 2009-09-18 at 12:15 -0500, Eric Evans wrote: > What say you? +1 -- Eric Evans eev...@rackspace.com
[VOTE] 0.4.0 Final
It's been a little over a week since we voted on RC2 here (http://www.mail-archive.com/cassandra-dev@incubator.apache.org/msg00887.html), and no show stoppers have cropped up. I propose we release as final what is currently in the cassandra-0.4 branch (r816701). The differences between rc2 are quite minimal and include the fix for CASSANDRA-440, some changes under contrib/, and an updated README.txt and CHANGES.txt. What say you? SVN Tag: https://svn.apache.org/repos/asf/incubator/cassandra/tags/cassandra-0.4.0-final/ 0.4.0 artifacts: http://people.apache.org/~eevans/ -- Eric Evans eev...@rackspace.com
[VOTE RESULTS] was: [VOTE] Release cassandra 0.4.0-rc2
The vote is now closed with the following results: * +1 votes: 4 (Ant Elder, Paul Querna, Leo Simons, Matthieu Riou) * 0 votes: 0 * -1 votes: 0 The vote passes. Thanks everyone. On Fri, 2009-09-11 at 12:14 -0500, Eric Evans wrote: > The Cassandra community voted on and approved the release of Apache > Cassandra 0.4.0-rc2. We would now like to request the approval of the > Incubator PMC for this release. > > Cassandra is a massively scalable, eventually consistent, distributed, > structured key-value store. > > Podling vote thread: > http://www.mail-archive.com/cassandra-dev@incubator.apache.org/msg00887.html > 0.4.0-rc2 artifacts: http://people.apache.org/~eevans > SVN tag: > https://svn.apache.org/repos/asf/incubator/cassandra/tags/cassandra-0.4.0-rc2 > Project home: http://incubator.apache.org/cassandra/ > Incubation status: http://incubator.apache.org/projects/cassandra.html > > The vote will remain open for 72 hours (or longer if needed). > > There were a number of changes made since RC1 to address concerns raised > in previous votes. Among them: > > * License texts in lib/licenses where removed and incorporated into a > monolithic top-level LICENSE.txt. CASSANDRA-371 > > * Attributions for all third-party code was added to the top-level > NOTICE.txt file. CASSANDRA-371 > > * Commons javaflow was removed. CASSANDRA-428 > > * The developers/contributors reference in NOTICE.txt was removed, (as > was the actual list in pom.xml). CASSANDRA-415 > > * Missing SVN properties that had crept in were added, and project > documentation updated. CASSANDRA-429 > > Regards, -- Eric Evans eev...@rackspace.com
Re: Calling all mentors
On Wed, 2009-09-16 at 08:24 -0700, Matthieu Riou wrote: > Sorry for the lateness. Thanks Matthieu. -- Eric Evans eev...@rackspace.com
Re: [VOTE] Release cassandra 0.4.0-rc2
On Mon, 2009-09-14 at 16:24 +0100, Leo Simons wrote: > Hrmpf, not sure. Since they're in a gen-java directory its pretty > obvious what the story with them is, but CLILexer.java also misses a > license header, which makes *me* whinge just enough to not give a +1, > but that's also because I don't know much about the provenance of the > codebase. You might get +1s from other folks, you did before, the > files are there in the 0.3.x :) None of the generated files contain license headers and my understanding was that they were exempt from this, (and even the output of Rat seems support this). Sebb's point was that they were included in the source archive but are not checked into SVN (i.e. because they were generated during release), which is certainly true. I'm curious though, when you say "...which makes me whinge just enough to not give a +1", is that hypothetical, or is there feedback that we could incorporate so that you would actually vote for our release? -- Eric Evans eev...@rackspace.com
Re: [VOTE] Release cassandra 0.4.0-rc2
On Mon, 2009-09-14 at 08:52 +0100, sebb wrote: > > The source archive contains 3 files that are not in SVN: > > Cli.tokens > CliLexer.java > CliParser.java > > These are generated files. > > Either store the files in SVN and release them, or remove them from > the release. I think everyone sort of forgot about these, (there is an open issue on this, CASSANDRA-316); is this considered blocking? > [I'm not quite sure why you need these files anyway, given that you > also depend on commons-cli.] There is no overlap. These files are generated by ANTLR to parse text interactively typed at the console, not parse the arguments passed on the command line. -- Eric Evans eev...@rackspace.com
[VOTE] Release cassandra 0.4.0-rc2
The Cassandra community voted on and approved the release of Apache Cassandra 0.4.0-rc2. We would now like to request the approval of the Incubator PMC for this release. Cassandra is a massively scalable, eventually consistent, distributed, structured key-value store. Podling vote thread: http://www.mail-archive.com/cassandra-dev@incubator.apache.org/msg00887.html 0.4.0-rc2 artifacts: http://people.apache.org/~eevans SVN tag: https://svn.apache.org/repos/asf/incubator/cassandra/tags/cassandra-0.4.0-rc2 Project home: http://incubator.apache.org/cassandra/ Incubation status: http://incubator.apache.org/projects/cassandra.html The vote will remain open for 72 hours (or longer if needed). There were a number of changes made since RC1 to address concerns raised in previous votes. Among them: * License texts in lib/licenses where removed and incorporated into a monolithic top-level LICENSE.txt. CASSANDRA-371 * Attributions for all third-party code was added to the top-level NOTICE.txt file. CASSANDRA-371 * Commons javaflow was removed. CASSANDRA-428 * The developers/contributors reference in NOTICE.txt was removed, (as was the actual list in pom.xml). CASSANDRA-415 * Missing SVN properties that had crept in were added, and project documentation updated. CASSANDRA-429 Regards, -- Eric Evans eev...@rackspace.com
[CANCELLED] ([VOTE] Release cassandra 0.4.0-rc1)
This vote is being cancelled because it was lapped by the next proposed release candidate, (and because no one would vote for it). On Thu, 2009-09-03 at 10:40 -0500, Eric Evans wrote: > The Cassandra community voted on and approved the release of Apache > Cassandra 0.4.0-rc1. We would now like to request the approval of the > Incubator PMC for this release. > > Cassandra is a massively scalable, eventually consistent, distributed, > structured key-value store. > > Podling vote thread: > http://www.mail-archive.com/cassandra-dev@incubator.apache.org/msg00856.html > 0.4.0-rc1 artifacts: http://people.apache.org/~eevans > SVN tag: > https://svn.apache.org/repos/asf/incubator/cassandra/tags/cassandra-0.4.0-rc1 > Project home: http://incubator.apache.org/cassandra/ > Incubation status: http://incubator.apache.org/projects/cassandra.html > > The vote will remain open for 72 hours (or longer if needed). -- Eric Evans eev...@rackspace.com
Re: [VOTE] 0.4.0 RC2
On Thu, 2009-09-10 at 12:56 -0500, Eric Evans wrote: > SVN Tag: > https://svn.apache.org/repos/asf/incubator/cassandra/tags/cassandra-0.4.0-rc2 > 0.4.0-rc2 artifacts: http://people.apache.org/~eevans/ +1 -- Eric Evans eev...@rackspace.com
[VOTE] 0.4.0 RC2
It's been a little over a week since we voted for, and passed, 0.4.0 RC1 on this list. A vote on RC1 was also taken to the Incubator PMC, though that has yet to go anywhere (it's only garnered one vote so far). Since then a few bugs have been addressed, the most noteworthy being https://issues.apache.org/jira/browse/CASSANDRA-418. There have also been some changes that will hopefully result in more IPMC votes for this and future releases (see CASSANDRA-429, CASSANDRA-371, CASSANDRA-415, and CASSANDRA-428). SVN Tag: https://svn.apache.org/repos/asf/incubator/cassandra/tags/cassandra-0.4.0-rc2 0.4.0-rc2 artifacts: http://people.apache.org/~eevans/ -- Eric Evans eev...@rackspace.com
Re: Review of cassandra NOTICE and LICENSE requested.
On Wed, 2009-09-09 at 17:23 +0100, sebb wrote: > > We have a source and binary distribution with the same NOTICE and > > LICENSE texts in both artifacts. While we don't want/need to ship > the > > junit jar in the binary distribution (see CASSANDRA-417), shipping > it in > > the source artifact is intentional. > > > > That's not normal; the source artifact should only contain files which > are in SVN and the JUnit jar should not be in SVN. This is > particularly true since you are using Maven which will fetch any > required dependencies when doing a build. The pom.xml file was added at the request of a user; I wouldn't characterize us a "Maven project", (I for example do not use it). -- Eric Evans eev...@rackspace.com
Re: Review of cassandra NOTICE and LICENSE requested.
On Tue, 2009-09-08 at 22:28 +0100, sebb wrote: > Does the release actually *include* JUnit, or is that only used for > testing? If so, then it should not be the in the NOTICE file, nor in > the binary release. We have a source and binary distribution with the same NOTICE and LICENSE texts in both artifacts. While we don't want/need to ship the junit jar in the binary distribution (see CASSANDRA-417), shipping it in the source artifact is intentional. > Is ANTLR actually needed at run-time, or is it only needed for > building the code? It's only used to build. > I'm not sure whether it needs to be mentioned in NOTICE if it is only > used at build-time. I had thought it was needed when redistributing code with the terms that require it (and as far as I know, that's only Apache License 2.0). I was told on this list (repeatedly), that I was wrong. Now I'm just confused. Again. > It should not be in the binary release if it's not needed at run-time. Agreed (CASSANDRA-417), but again, shipping a copy in the source artifact is intentional, (hence the entries in NOTICE and LICENSE). > The NOTICE file mentions SLF4J, which AIUI is a logging abstraction - > does the binary release include a logging implementation? If so, it > will need to be documented in the LICENSE and NOTICE. We use log4j for logging, but we require/ship thrift which in turn requires slf4j. > > It would be great if we could get these reviewed ahead of time so > that > > any feedback could be incorporated before the next release vote. > > It's not possible to be definitive about the files without knowing > what libraries are actually going to be included in the binary > release. There haven't been any changes since the last review, (see https://svn.apache.org/repos/asf/incubator/cassandra/trunk/lib). Thanks for taking the time to look at this. -- Eric Evans eev...@rackspace.com
Review of cassandra NOTICE and LICENSE requested.
Attached are draft copies of LICENSE and NOTICE files for the cassandra project. LICENSE is monolithic, it contains a copy of all licenses. It is meant to replace the texts we currently keep in lib/licenses. NOTICE contains an entry for all the third-party libraries in our tree (in so much as that information is available). It would be great if we could get these reviewed ahead of time so that any feedback could be incorporated before the next release vote. Thanks in advance, -- Eric Evans eev...@rackspace.com Apache License Version 2.0, January 2004 http://www.apache.org/licenses/ TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION 1. Definitions. "License" shall mean the terms and conditions for use, reproduction, and distribution as defined by Sections 1 through 9 of this document. "Licensor" shall mean the copyright owner or entity authorized by the copyright owner that is granting the License. "Legal Entity" shall mean the union of the acting entity and all other entities that control, are controlled by, or are under common control with that entity. For the purposes of this definition, "control" means (i) the power, direct or indirect, to cause the direction or management of such entity, whether by contract or otherwise, or (ii) ownership of fifty percent (50%) or more of the outstanding shares, or (iii) beneficial ownership of such entity. "You" (or "Your") shall mean an individual or Legal Entity exercising permissions granted by this License. "Source" form shall mean the preferred form for making modifications, including but not limited to software source code, documentation source, and configuration files. "Object" form shall mean any form resulting from mechanical transformation or translation of a Source form, including but not limited to compiled object code, generated documentation, and conversions to other media types. "Work" shall mean the work of authorship, whether in Source or Object form, made available under the License, as indicated by a copyright notice that is included in or attached to the work (an example is provided in the Appendix below). "Derivative Works" shall mean any work, whether in Source or Object form, that is based on (or derived from) the Work and for which the editorial revisions, annotations, elaborations, or other modifications represent, as a whole, an original work of authorship. For the purposes of this License, Derivative Works shall not include works that remain separable from, or merely link (or bind by name) to the interfaces of, the Work and Derivative Works thereof. "Contribution" shall mean any work of authorship, including the original version of the Work and any modifications or additions to that Work or Derivative Works thereof, that is intentionally submitted to Licensor for inclusion in the Work by the copyright owner or by an individual or Legal Entity authorized to submit on behalf of the copyright owner. For the purposes of this definition, "submitted" means any form of electronic, verbal, or written communication sent to the Licensor or its representatives, including but not limited to communication on electronic mailing lists, source code control systems, and issue tracking systems that are managed by, or on behalf of, the Licensor for the purpose of discussing and improving the Work, but excluding communication that is conspicuously marked or otherwise designated in writing by the copyright owner as "Not a Contribution." "Contributor" shall mean Licensor and any individual or Legal Entity on behalf of whom a Contribution has been received by Licensor and subsequently incorporated within the Work. 2. Grant of Copyright License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare Derivative Works of, publicly display, publicly perform, sublicense, and distribute the Work and such Derivative Works in Source or Object form. 3. Grant of Patent License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable (except as stated in this section) patent license to make, have made, use, offer to sell, sell, import, and otherwise transfer the Work, where such license applies only to those paten
[VOTE] Release cassandra 0.4.0-rc1
The Cassandra community voted on and approved the release of Apache Cassandra 0.4.0-rc1. We would now like to request the approval of the Incubator PMC for this release. Cassandra is a massively scalable, eventually consistent, distributed, structured key-value store. Podling vote thread: http://www.mail-archive.com/cassandra-dev@incubator.apache.org/msg00856.html 0.4.0-rc1 artifacts: http://people.apache.org/~eevans SVN tag: https://svn.apache.org/repos/asf/incubator/cassandra/tags/cassandra-0.4.0-rc1 Project home: http://incubator.apache.org/cassandra/ Incubation status: http://incubator.apache.org/projects/cassandra.html The vote will remain open for 72 hours (or longer if needed). There was quite a bit of discussion surrounding the last IPMC vote, so here is a list of some of the things that were brought up, and where we are are on those issues: * No zip archives We are still not generating zip archives. Hopefully that won't be an issue. * Missing SVN properties This was addressed in CASSANDRA-368 (i.e. the properties are now in place). * Licenses in lib/licenses instead of LICENSE.txt During the discussion, CASSANDRA-371 was created and a reference has since been added to the bottom of LICENSE.txt that directs people to lib/licenses for the third-party dependencies. The reason for putting third-party licenses in lib/licenses was to ease maintenance, which in turn should help guarantee that this information is up-to-date and accurate. That still seems like a valid reason so if possible, I'd like to wait for the resolution of LEGAL-31 * JUnit jar in binary archive I completely lost track of this after the discussion, and didn't notice it until after 0.4.0-rc1 was tagged and the artifacts created. I've submitted CASSANDRA-417 so that it won't be forgotten again. * Attributions in NOTICE.txt During the discussion, I explained the rationale[1] behind our NOTICE.txt, but I'm not sure that went anywhere. The example cited was Antlr, but by my understanding of the BSD license, there is no requirement that the attribution be in a top-level file let alone one named NOTICE.txt. Again, we're trying to keep things simple so that it is easier to maintain and as a result, more accurate and up-to-date. But, if this is a sore spot with IPMC voters, we'll put all attributions, required or not in NOTICE.txt. * NOTICE shouldn't have "Developers and Contributors are listed in..." This is another one I lost track of after the discussion, (CASSANDRA-415 submitted). [1] http://www.mail-archive.com/gene...@incubator.apache.org/msg22190.html Regards, -- Eric Evans eev...@rackspace.com
Re: [VOTE] 0.4 RC1
On Wed, 2009-09-02 at 10:44 -0500, Jonathan Ellis wrote: > We've fixed a lot of bugs from our beta release and Digg is now > running 0.4 in production. I think we're ready to put out a release > candidate for a final bug catching period before -final. > > Notable bug fixes include > https://issues.apache.org/jira/browse/CASSANDRA-405 > https://issues.apache.org/jira/browse/CASSANDRA-392 > https://issues.apache.org/jira/browse/CASSANDRA-337 > https://issues.apache.org/jira/browse/CASSANDRA-367 > > Additionally, Sandeep finished up the bootstrap code, so 0.4 now > supports adding nodes to a running cluster. (Start a new node with > the -b flag to make it contact the appropriate other nodes and tell > them to send it data.) Some additional refinement of bootstrap is > scheduled for 0.5 but the basics are in 0.4. +1 (binding) -- Eric Evans eev...@rackspace.com
Re: [VOTE] Change data model names for 0.5
On Mon, 2009-08-24 at 12:29 -0700, Evan Weaver wrote: > Resolved, that the data model names should be changed in Cassandra > 0.5. -1 -- Eric Evans eev...@rackspace.com
Re: Data model names, reloaded
On Mon, 2009-08-24 at 08:50 -0700, Ryan King wrote: > We have never indicated that we expected others to do the work. I > actually have some patches for our first renaming suggestion already, > but given the massive size of the change, we though it prudent to > discuss it with others before investing the time in making the change. > I've set aside several days this week just to work on patches for > this. To me, it's no consolation that you guys are willing to make the source and documentation changes. It doesn't matter *who* makes them, the amount of churn is going to be enormous, the proposed changes are very destabilizing, and I would argue that the current naming is so entrenched that no matter how thorough you think you are being, context will be lost. There is also all sorts of "documentation" that is beyond your control to change. Presentation materials, videos, blog postings, etc will all be rendered moot the moment changes like these occur. That's not to mention all of the current users who will now be forced to rewire their brains to understand the new terminology. Now the argument as I understand it is that the proposed naming is so much more succinct, that it will make Cassandra so much easier for people to understand, that it warrants all of this cost. That it will be worth it in the long term. I disagree. It isn't clear to me that the proposed names are *any* better than what we have, let alone that they warrant this sort of disruptive change -- Eric Evans eev...@rackspace.com
Re: credit where it's due
On Thu, 2009-08-20 at 15:01 -0700, Jonathan Ellis wrote: > Thanks to our mentor Ant Elder for trying to improve the incubation > experience for us and others. (Re the recent activity on > incubator-general.) Full ACK. Thanks for your all your efforts ant! -- Eric Evans eev...@rackspace.com
Re: Cassandra data model misconceptions, and their sources
On Mon, 2009-08-17 at 15:32 -0700, Mark McBride wrote: > My first attempt at a revamped data model wiki page is up here > > http://wiki.apache.org/cassandra/DataModel2 I think you are on the right track. Very nice. -- Eric Evans eev...@rackspace.com
[VOTE RESULTS] was: [VOTE] Release cassandra 0.4.0-beta1
The vote is now closed with the following results: * +1 votes: 3 (Matthias Wessendorf, Ant Elder, Ian Holsman) * 0 votes: 0 * -1 votes: 0 The vote passes. Thanks everyone. On Fri, 2009-08-14 at 15:08 -0500, Eric Evans wrote: > The Cassandra community voted on and approved the release of Apache > Cassandra 0.4.0-beta1. We would now like to request the approval of the > Incubator PMC for this release. > > Cassandra is a massively scalable, eventually consistent, distributed, > structured key-value store. > > Podling Vote thread: > http://www.mail-archive.com/cassandra-dev@incubator.apache.org/msg00639.html > 0.4.0-beta1 artifacts: http://people.apache.org/~eevans > SVN Tag: > http://svn.apache.org/repos/asf/incubator/cassandra/tags/cassandra-0.4.0-beta1 > Project home: http://incubator.apache.org/cassandra/ > Incubation status: http://incubator.apache.org/projects/cassandra.html -- Eric Evans eev...@rackspace.com
