Please unsubscribe me from the email list.
Please unsubscribe gary.mo...@xerox.com from this email list. Thank you.
Re: [VOTE] 0.7.1 (what are we at now, 4?)
+1 On Thu, Feb 10, 2011 at 11:52 AM, Eric Evans eev...@rackspace.com wrote: I propose the following for release as 0.7.1. SVN: https://svn.apache.org/repos/asf/cassandra/branches/cassandra-0.7@r1069461 0.7.1 artifacts: http://people.apache.org/~eevans The vote will be open for 72 hours. [1]: http://goo.gl/5VAPP (CHANGES.txt) [2]: http://goo.gl/C9M5W (NEWS.txt) [3]: http://goo.gl/8dZUr -- Eric Evans eev...@rackspace.com
Re: [VOTE] 0.7.1 (what are we at now, 4?)
+1 Tested reading 0.7.0 commitlog and data files and compacting to new bloom filter format. On Thu, Feb 10, 2011 at 11:52 AM, Eric Evans eev...@rackspace.com wrote: I propose the following for release as 0.7.1. SVN: https://svn.apache.org/repos/asf/cassandra/branches/cassandra-0.7@r1069461 0.7.1 artifacts: http://people.apache.org/~eevans The vote will be open for 72 hours. [1]: http://goo.gl/5VAPP (CHANGES.txt) [2]: http://goo.gl/C9M5W (NEWS.txt) [3]: http://goo.gl/8dZUr -- Eric Evans eev...@rackspace.com -- Jonathan Ellis Project Chair, Apache Cassandra co-founder of DataStax, the source for professional Cassandra support http://www.datastax.com
Re: [VOTE] 0.7.1 (what are we at now, 4?)
+1 Seeing some impressive performance improvements in my use case. -Jake On Mon, Feb 14, 2011 at 10:21 AM, Jonathan Ellis jbel...@gmail.com wrote: +1 Tested reading 0.7.0 commitlog and data files and compacting to new bloom filter format. On Thu, Feb 10, 2011 at 11:52 AM, Eric Evans eev...@rackspace.com wrote: I propose the following for release as 0.7.1. SVN: https://svn.apache.org/repos/asf/cassandra/branches/cassandra-0.7@r1069461 0.7.1 artifacts: http://people.apache.org/~eevans The vote will be open for 72 hours. [1]: http://goo.gl/5VAPP (CHANGES.txt) [2]: http://goo.gl/C9M5W (NEWS.txt) [3]: http://goo.gl/8dZUr -- Eric Evans eev...@rackspace.com -- Jonathan Ellis Project Chair, Apache Cassandra co-founder of DataStax, the source for professional Cassandra support http://www.datastax.com
Re: Maintenance releases
As a user, this sounds like great news. To see the consensus on this issue is reassuring. For me, release stability and planning are more important that new features. I would rather wait longer for the features if it means I'm getting a solid release. It would be great if there were some clearing of the air with respect to release discipline going forward. Granted, there was a time when everybody expected there to be hard and fast changes, as Cassandra was relatively new on the landscape. I think we are past that expectation now, or at least to the knee of the curve. On Fri, Feb 11, 2011 at 1:36 PM, Jeremy Hanna jeremy.hanna1...@gmail.com wrote: strong unbinding +1 :) I think that there were several lessons learned in the 0.6.x line about walking that line. Wrt regression testing, hopefully the distributed tests (thanks Stu and Kelvin and others!) will act as a core for something like that. I would imagine that heavy loads can be utilized in there as well. On Feb 11, 2011, at 12:19 PM, Jake Luciani wrote: +1 I'm also concerned with our lack of regression testing. A lot of this is done by individual committers firing up EC2 clusters and running basic sanity checks and workloads. Most of the bugs we are finding pop up under heavy load. It would be great if the community could identify and contribute use cases that could be bundled into a regression test suite. On Fri, Feb 11, 2011 at 11:35 AM, Gary Dusbabek gdusba...@gmail.com wrote: I've been uncomfortable with the amount of features I perceive are going into our maintenance releases for a while now. I thought it would stop after we committed ourselves to having a more predictable major release schedule. But getting 0.7.1 out feels like it's taken a lot more effort than it should have. I wonder if part of the problem is that we've been committing destabilizing features into it? IMO, maintenance releases (0.7.1, 0.7.2, etc.) should only contain bug fixes and *carefully* vetted features. I've scanned down the list of 0.7.1 changes in CHANGES.txt and about half of them are features that I think could have stayed in trunk. I think we did this a lot with the early maintenance releases of 0.6 as well, probably in an effort to get features out *now* instead of waiting for an 0.7 that was not happening soon enough. We've decided to pick up the pace of our major release schedule (sticking to four months). I think maintaining this pace will be difficult if we continue to commit as many features into the minor releases as we have been. I'm willing to concede that I may have an abnormally conservative opinion about this. But I wanted to voice my concern in hopes we can improve the quality and delivery of our maintenance releases. Gary.
Re: New feature / educational project
As a suggestion for one possible approach to this: I've used the excellent MVEL (expression language) as a tool for dynamic scripting which can compile and be VM optimized to near-native speed. This may provide a means to implement dynamic-yet-efficient event handling into client or server logic. Trade-offs: 1) -- Eclipse and other tools will not provide you with the same level of compile-time checking. 2) ++ Application-level expressions can be injected into control points which are exposed via your app with little (almost none) loss of performance. Even as an intermediate representation, it can be rendered from a marshaled/constrained representation at app-level, providing more robustness to the user. It can do more than just return values (as an expression language), actually acting as a light-weight scripting language. I am not affiliated with this project. I have just had very good results with this tool after surveying the expression language landscape. Performance, flexibility and ease of integration were my criteria, in order of preference. On Wed, Feb 9, 2011 at 10:04 AM, Dave Revell d...@meebo-inc.com wrote: +1 for interest. This feature would be great if done well. On Feb 8, 2011 11:54 PM, m...@monit.dk m...@monit.dk wrote: I noticed :) But the question was if such a feature could make it to the trunk - and as far as I see, there is enough interest around this. - Reply message - From: Tristan Tarrant tristan.tarr...@gmail.com Date: Wed, Feb 9, 2011 05:56 Subject: New feature / educational project To: dev@cassandra.apache.org With Java 6 there is no need to add rhino as there already is the javax.script package Tristan On Feb 8, 2011 9:56 PM, Morten Wegelbye Nissen m...@monit.dk wrote: Hello mighty developers of Cassandra, I have been thinking of creating a feature like stored procedures for Cassandra. Concept is actually pretty simple add one of the javascript compilers. ( Mozilla Rhino or one alike ). Save js source in a CF in the system keyspace. Add feature to thrift to invoke the code. Return just like get_slice. Needless to say that the execution environment needs access to the keyspaces and needs to be sandboxed. (ie. no access to filesystem etc. ) On the cli it would be something like; invoke myProc param1, param2, param3 The alternative where the expansions, like the existing once, is done by implementing interfaces. Would require a rather complex distribution of jars. Now I might have the option to get this done as a educational project, where I after the project would like to release the code to freedom. Would a feature like that ever make it to the core of Cassandra? ./Morten
[VOTE RESULT] was: [VOTE] 0.7.1 (what are we at now, 4?)
On Thu, 2011-02-10 at 11:52 -0600, Eric Evans wrote: SVN: https://svn.apache.org/repos/asf/cassandra/branches/cassandra-0.7@r1069461 0.7.1 artifacts: http://people.apache.org/~eevans The vote will be open for 72 hours. By my count that's 5 binding +1s, 2 others, and no -1s; The vote passes. I'll start work on publishing everything. -- Eric Evans eev...@rackspace.com
Re: [VOTE RESULT] was: [VOTE] 0.7.1 (what are we at now, 4?)
I'll publish to maven central - Stephen --- Sent from my Android phone, so random spelling mistakes, random nonsense words and other nonsense are a direct result of using swype to type on the screen On 14 Feb 2011 19:20, Eric Evans eev...@rackspace.com wrote:
Re: Maintenance releases
On Fri, Feb 11, 2011 at 8:35 AM, Gary Dusbabek gdusba...@gmail.com wrote: I've been uncomfortable with the amount of features I perceive are going into our maintenance releases for a while now. [...] IMO, maintenance releases (0.7.1, 0.7.2, etc.) should only contain bug fixes and *carefully* vetted features. [...] I'm willing to concede that I may have an abnormally conservative opinion about this. But I wanted to voice my concern in hopes we can improve the quality and delivery of our maintenance releases. It should surprise almost no-one that I am +1 on the above. :) I'd like to also mention a potential semantic challenge regarding bug-fix releases. Once a bug-fix is over a certain scope, or involves a new technique to solve the old problem, it may qualify as a refactor instead of a bug-fix. I believe that we would benefit by consciously attempting to avoid refactors while doing bug-fix release. I understand that the above is semantic squish, but I think the concepts can be a useful part of this discussion. Peter Schuller also said : For example, from the point of view of the user, I think that things like CASSANDRA-1992 should preferably result in an almost immediate bugfix-only release with instructions and impact information for users. +1 this very much, from an ops/DBA perspective. If, for example, upgrading to a version can BREAK YOUR STORED DATA PERMANENTLY UNDER NORMAL OPERATING CONDITIONS, that version should either be immediately superceded by a paper-bag release containing only the relevant fix, or a GIANT BLINKING RED WARNING should be posted everywhere indicating its known-unsafeness. =Rob
Re: Are there any tickets that I can work on
In general, patches that improve the error messages from the CLI for bad syntax would surely be appreciated. e.g. instead of missing EOF at blah maybe expeced 'with' after keyspace name On Mon, Feb 14, 2011 at 10:17 AM, Eranda Sooriyabandara 0704...@gmail.comwrote: Hi all, Now I am quite comfortable with the Cassandra API and Cassandra-cli. So I am hoping to work on some tickets which are appropriate for a newcomer to getting know about the code. Since I am interested in cassandra-cli if it is a ticket related to it, that would be great. thanks Eranda
