In NEWS.txt the second 2.0.8 should be an earlier version.
2.0.8
=
...
Upgrading
-
- Nothing specific to this release, but please see 2.0.8 if you are
upgrading
from a previous version.
Blair
On May 6, 2014, at 2:12 AM, Sylvain Lebresne wrote:
> Since a fair amount of b
On Dec 19, 2013, at 11:40 AM, Andy Cobley
wrote:
> The question just as easily be asked, why not rewrite it in Erlang ?
> Probably lots of advantages to be gained there, the ability to upgrade on the
> fly, native message passing, functional programming paradigm ?
You could switch from Jav
On 09/04/2013 12:08 AM, Sylvain Lebresne wrote:
I would venture that either your local copy or whatever your 'origin'
points to is not up to date. There was a cassandra-2.0.0 prior to the final
2.0 release and it was both a tag and a branch name for about 10 minutes
but the branch has been remove
$ git branch -a | grep cassandra-2.0.0
* cassandra-2.0.0
remotes/origin/cassandra-2.0.0
$ git tag -l | grep cassandra-2.0.0cassandra-2.0.0
cassandra-2.0.0-beta1
cassandra-2.0.0-beta2
cassandra-2.0.0-rc1
cassandra-2.0.0-rc2
$ git checkout cassandra-2.0.0
warning: refname 'cassandra-2.0.0' is am
Opened https://issues.apache.org/jira/browse/CASSANDRA-5619
Blair
On 06/05/2013 12:23 AM, Sylvain Lebresne wrote:
Doesn't sound like a bad idea to me a priori. Would you mind opening a JIRA
ticket for that so it doesn't fell through the cracks?
Hello,
Looking at the new CAS CQL3 support examples [1], if one lost a race for
an UPDATE, to save a round trip to get the current values, could the
columns that were used in the IF clause also be returned to the caller?
Maybe the columns values as part of the SET part could also be returned.
