https://issues.apache.org/jira/browse/CASSANDRA-918
Someone seems to be working on the idea. Don't know what's the status exactly.
On Mon, May 3, 2010 at 12:49 PM, Ran Tavory ran...@gmail.com wrote:
I'd be happy to get a management web interface on each cassandra node so i
can easily (and
What would be the pros of breaking it for 0.7 now ?
I suppose you have something specific in mind that would break
compatibility ?
On Thu, Jul 22, 2010 at 8:19 PM, Gary Dusbabek gdusba...@gmail.com wrote:
I think this depends on how much value users place in rolling upgrades
(it's going to
+1
On Tue, Aug 10, 2010 at 8:14 PM, Jonathan Ellis jbel...@gmail.com wrote:
+1
On Tue, Aug 10, 2010 at 1:51 PM, Vijay vijay2...@gmail.com wrote:
+1
Regards,
/VJ
On Tue, Aug 10, 2010 at 10:20 AM, Eric Evans eev...@rackspace.com wrote:
Today is the Cassandra Summit in San Francisco,
In CASSANDRA-1546, I propose an alternative to #1072. At it's core,
it rewrites #1072 without the clocks structure (by splitting the clock into
individual columns, not unlike what Zhu Han proposed in his preceding
mail, but in a row instead of a super column, for reason explained in the
issue).
I agree that it is worth adding a support for counter as supercolumns
in 1546 and that's fairly trivial, so I will add that as soon as possible
(but please understand that I'm working on this for a good part during
my free time).
As for supercolumns of counters, there is what Jonathan proposes,
On Thu, Sep 30, 2010 at 6:29 PM, Ryan King r...@twitter.com wrote:
On Tue, Sep 28, 2010 at 10:14 PM, Jonathan Ellis jbel...@gmail.com wrote:
On Tue, Sep 28, 2010 at 4:00 PM, Sylvain Lebresne sylv...@yakaz.com wrote:
I agree that it is worth adding a support for counter as supercolumns
in 1546
On Fri, Oct 1, 2010 at 5:12 PM, Zhu Han schumi@gmail.com wrote:
They have however at least one advantage:
- your super columns are indexed, you don't have to deserialize them
entirely each time.
The size of counter super column is limited to how many replicas propagated
values as
:26 AM, Sylvain Lebresne sylv...@yakaz.com wrote:
I think Hinted handoff are buggy in current rc1-snapshot
(see https://issues.apache.org/jira/browse/CASSANDRA-1672).
I think this pretty much prevent hints from being delivered. Don't
know if that is considered harmful enough to re-roll RC1
+1 (not binding)
On Thu, Jan 6, 2011 at 7:07 PM, Brandon Williams dri...@gmail.com wrote:
+1, for reals yo.
On Thu, Jan 6, 2011 at 11:17 AM, Eric Evans eev...@rackspace.com wrote:
RC 4 seems to be holding up OK, shall we? I propose the following for
release as 0.7.0 (aka For Reals
+1
On Tue, Feb 15, 2011 at 10:57 PM, Eric Evans eev...@rackspace.com wrote:
CASSANDRA-2165[1] is troublesome enough to warrant a new release. I
propose the following for 0.7.2.
SVN:
https://svn.apache.org/repos/asf/cassandra/branches/cassandra-0.7.2@r1071063
0.7.2 artifacts:
+1
On Sun, Feb 27, 2011 at 2:15 AM, Stephen Connolly
stephen.alan.conno...@gmail.com wrote:
On 25 February 2011 21:09, Eric Evans eev...@rackspace.com wrote:
Shall we? I propose the following for release as 0.7.3.
SVN:
+1
On Mon, Mar 14, 2011 at 11:17 PM, Gary Dusbabek gdusba...@gmail.com wrote:
+1
On Mar 11, 2011 6:47 PM, Eric Evans eev...@rackspace.com wrote:
It's that time again. I propose the following for release as 0.7.4.
What say you?
SVN:
+1
On Tue, Apr 19, 2011 at 3:10 PM, Stephen Connolly
stephen.alan.conno...@gmail.com wrote:
FYI: http://www.apache.org/foundation/voting.html#ReleaseVotes
quoteReleases may not be vetoed/quote
On 19 April 2011 13:42, Shotaro Kamio kamios...@gmail.com wrote:
-1,
I'd like to make 0.8 to
+1
On Thu, Apr 21, 2011 at 2:27 PM, Gary Dusbabek gdusba...@gmail.com wrote:
+1
On Tue, Apr 19, 2011 at 20:35, Eric Evans eev...@rackspace.com wrote:
Let's try this again. I propose the following artifacts for release as
0.8.0 beta1.
You will note the addition of three new artifacts,
That susepaste url or yours don't show anything at all here, so can't help you.
--
Sylvain
On Fri, Apr 22, 2011 at 1:41 PM, Manu Gupta manugu...@gmail.com wrote:
Hi All
Recently I am trying to look into cassandra and I was trying to run
the stable version which I was able to do but I was not
by 'latest git version of it' (which branch that is).
--
Sylvain
On Fri, Apr 22, 2011 at 2:02 PM, Manu Gupta manugu...@gmail.com wrote:
I am sorry I updated it to the new URl
http://susepaste.org/47932397
On Fri, Apr 22, 2011 at 5:21 PM, Sylvain Lebresne sylv...@datastax.com
wrote
On Fri, 2011-04-22 at 19:17 +0200, Sylvain Lebresne wrote:
I propose the following artifacts for release as 0.7.5.
SVN:
https://svn.apache.org/repos/asf/cassandra/branches/cassandra-0.7@r1095960
Artifacts:
https://repository.apache.org/content/repositories/orgapachecassandra-113/org/apache
+1
On Tue, May 3, 2011 at 6:29 PM, Gary Dusbabek gdusba...@gmail.com wrote:
+1
On Mon, May 2, 2011 at 20:36, Eric Evans eev...@rackspace.com wrote:
I propose the following artifacts for release as 0.8.0 beta2.
SVN:
https://svn.apache.org/repos/asf/cassandra/branches/cassandra-0.8@r1098882
On Fri, May 6, 2011 at 5:33 AM, Dave Rav daver...@yahoo.com wrote:
can I use 'Colunm' and 'CounterColumn' in the same 'column family'?
No you cannot. As of 0.8.0 you have either counter column family or column
family without counters. But I'll admit that right off the bat I don't see any
I hate to ruin the party but I think that we may have to reroll for
https://issues.apache.org/jira/browse/CASSANDRA-2642
if we want to call this a release candidate.
--
Sylvain
On Thu, May 12, 2011 at 1:13 AM, Eric Evans eev...@rackspace.com wrote:
On Wed, 2011-05-11 at 16:23 +0100, Stephen
It's been only a little more than 2 weeks since the release of 0.7.5, but
since then we have corrected a handfull of fairly important bugs, incuding:
https://issues.apache.org/jira/browse/CASSANDRA-2554
https://issues.apache.org/jira/browse/CASSANDRA-2633
from the staging repository.
On 13 May 2011 10:39, Sylvain Lebresne sylv...@datastax.com wrote:
It's been only a little more than 2 weeks since the release of 0.7.5, but
since then we have corrected a handfull of fairly important bugs, incuding:
https://issues.apache.org/jira/browse/CASSANDRA
+1
On Mon, May 16, 2011 at 3:50 AM, Brandon Williams dri...@gmail.com wrote:
+¹
On May 12, 2011 7:14 PM, Eric Evans eev...@rackspace.com wrote:
OK, let's try this again; I propose the following artifacts for release
as 0.8.0 RC1.
SVN:
On Fri, May 13, 2011 at 11:39 AM, Sylvain Lebresne sylv...@datastax.com wrote:
It's been only a little more than 2 weeks since the release of 0.7.5, but
since then we have corrected a handfull of fairly important bugs, incuding:
https://issues.apache.org/jira/browse/CASSANDRA-2554
https
Release 0.7.6 shipped with a bug in the debian packaging that prevent the
package from being correctly set up (CASSANDRA-2481). Since the debian
packaging is in-tree, I'm not sure we have better choice than doing a new
release.
I thus propose the following artifacts for release as 0.7.6-2.
SVN:
Yeah, actually the fix to the fix of CASSANDRA-2626 had a typo too
(I fixed it directly in r1128460).
Moreover it turns out that CASSANDRA-2675 was a big problem for counters,
so I've committed it to the 0.8.0 branch too.
But -1 too on this release.
On Thu, May 26, 2011 at 4:09 AM, Brandon
We must also wait on CASANDRA-2653 to be reviewed and committed as it
is a serious one.
--
Sylvain
On Fri, May 27, 2011 at 11:17 PM, Sylvain Lebresne sylv...@datastax.com wrote:
Yeah, actually the fix to the fix of CASSANDRA-2626 had a typo too
(I fixed it directly in r1128460).
Moreover
+1
On Tue, May 31, 2011 at 3:25 AM, Chris Goffinet c...@chrisgoffinet.com wrote:
+1
-Chris
On May 30, 2011, at 12:04 PM, Eric Evans wrote:
OK, let's try this yet again; I propose the following artifacts for release
as 0.8.0 (final).
SVN:
On Tue, Jun 7, 2011 at 3:18 PM, Jonathan Ellis jbel...@gmail.com wrote:
Sounds fine as far as it goes, but don't we want some concept of
branches/tags for driver releases too?
Our idea so far (Eric can correct me if I'm wrong :)) was to consider
the drivers directory as the 'trunk' for drivers,
It's the two weeks anniversary of the release of Cassandra 0.8.0. And in the
meantime there has been a fair number of bug fixes and improvements.
I thus propose the following artifacts for release as 0.8.1.
SVN: https://svn.apache.org/repos/asf/cassandra/branches/cassandra-0.8@r1136328
Ladies and Gentlemen,
Cassandra 0.8 is now out and we'll hopefully soon have the first minor release
on that branch out too. It is now time to think of the next iteration, aka
Apache Cassandra 1.0 (sounds amazing...).
The 0.8 release was our first release on our new fixed 4 months release
, Sylvain Lebresne sylv...@datastax.com
wrote:
It's the two weeks anniversary of the release of Cassandra 0.8.0. And in the
meantime there has been a fair number of bug fixes and improvements.
I thus propose the following artifacts for release as 0.8.1.
SVN:
https://svn.apache.org/repos/asf
Yes, there has been a change of the messaging server version
between 0.8.0 and 0.8.1.
--
Sylvain
On Mon, Jun 20, 2011 at 5:10 PM, Peter Schuller
peter.schul...@infidyne.com wrote:
If things are working properly, he shouldn't see any of these messages
on a minor version upgrade because the
Let's try that again. I propose the following artifacts for release as 0.8.1:
SVN: https://svn.apache.org/repos/asf/cassandra/branches/cassandra-0.8@r1137891
Artifacts:
https://repository.apache.org/content/repositories/orgapachecassandra-030/org/apache/cassandra/apache-cassandra/0.8.1/
Staging
This did not took long, but I think we should probably re-roll this one for
https://issues.apache.org/jira/browse/CASSANDRA-2801
I'll wait for someone to confirm that I'm not smoking though.
--
Sylvain
On Tue, Jun 21, 2011 at 11:10 AM, Sylvain Lebresne sylv...@datastax.com wrote:
Let's try
Third time's the charm. I propose the following artifacts for release as 0.8.1:
SVN: https://svn.apache.org/repos/asf/cassandra/branches/cassandra-0.8@r1137891
Artifacts:
https://repository.apache.org/content/repositories/orgapachecassandra-031/org/apache/cassandra/apache-cassandra/0.8.1/
21, 2011 at 8:54 AM, Sylvain Lebresne sylv...@datastax.com
wrote:
Third time's the charm. I propose the following artifacts for release as
0.8.1:
SVN:
https://svn.apache.org/repos/asf/cassandra/branches/cassandra-0.8@r1137891
Artifacts:
https://repository.apache.org/content/repositories
Alright, third time's not always the charm, my mistake. Let's try again.
I propose the following artifacts for release as 0.8.1:
SVN:
https://svn.apache.org/repos/asf/cassandra/branches/cassandra-0.8.1@r1139326
Artifacts:
On Mon, Jun 27, 2011 at 12:45 PM, Peter Schuller
peter.schul...@infidyne.com wrote:
[1]: http://goo.gl/qbvPB (CHANGES.txt)
[2]: http://goo.gl/7uQXl (NEWS.txt)
CASSANDRA-2280 (https://issues.apache.org/jira/browse/CASSANDRA-2280)
is not listed (and I don't see the change in the branch), which
I propose the following artifacts for release as 0.7.7.
SVN: https://svn.apache.org/repos/asf/cassandra/branches/cassandra-0.7@r1143847
Artifacts:
https://repository.apache.org/content/repositories/orgapachecassandra-006/org/apache/cassandra/apache-cassandra/0.7.7/
Staging repository:
Oups. I've fixed this (more precisely, it will be fixed once the
apache mirrors are synced).
Hopefully 0.7.7 will be out soon enough anyway :)
--
Sylvain
On Fri, Jul 8, 2011 at 12:30 AM, Jeremy Hanna
jeremy.hanna1...@gmail.com wrote:
Not sure how long this has been the case, but the download
On Thu, Jul 7, 2011 at 5:14 PM, Sylvain Lebresne sylv...@datastax.com wrote:
I propose the following artifacts for release as 0.7.7.
SVN:
https://svn.apache.org/repos/asf/cassandra/branches/cassandra-0.7@r1143847
Artifacts:
https://repository.apache.org/content/repositories
Cassandra 0.7.7 has just been release, but a regression in it has been found
(hints are not delivered):
https://issues.apache.org/jira/browse/CASSANDRA-2928
The fixed has been committed and thus I propose the following artifacts for
release as 0.7.8.
SVN:
Cassandra 0.8.1 has been out for a few weeks now and we have had a number of
fixes since then. It feels like a good time to relase 0.8.2. But there is also
the fact that 0.8.1 suffers from the same regression than 0.7.7, that is:
https://issues.apache.org/jira/browse/CASSANDRA-2928
For both those
Including my own +1, I count 3 binding +1s and no -1s. The vote passes.
I'll get the artifacts published shortly.
On Thu, Jul 21, 2011 at 9:16 PM, Jonathan Ellis jbel...@gmail.com wrote:
+1
On Thu, Jul 21, 2011 at 10:11 AM, Sylvain Lebresne sylv...@datastax.com
wrote:
Cassandra 0.7.7 has
Adding my own vote, I count 3 binding +1s and no -1s. The vote passes.
I'll get the artifacts published.
--
Sylvain
On Fri, Jul 22, 2011 at 11:43 AM, Sylvain Lebresne sylv...@datastax.com wrote:
Cassandra 0.8.1 has been out for a few weeks now and we have had a number of
fixes since
We have found and fixed (CASSANDRA-2829) a regression of 0.8, due to
CASSANDRA-2419, causing commit log segments to be potentially deleted while
still dirty. There has been a number of other important bug fixes since 0.8.2,
including the fix of remove token.
I thus propose the following artifacts
2, 2011 at 1:28 PM, Sylvain Lebresne sylv...@datastax.com wrote:
We have found and fixed (CASSANDRA-2829) a regression of 0.8, due to
CASSANDRA-2419, causing commit log segments to be potentially deleted while
still dirty. There has been a number of other important bug fixes since
0.8.2
As mentionned when closing the previous vote, the preceding artifacts had a
regression, see:
https://issues.apache.org/jira/browse/CASSANDRA-2992
due to:
https://issues.apache.org/jira/browse/CASSANDRA-2785
The following artifacts are based on the artifacts of the previous 0.8.3 vote
from which I
Adding my own +1, I'm counting 3 binding +1's and no -0s, the vote passes.
I will get the artifacts published shortly.
On Mon, Aug 8, 2011 at 8:39 PM, Brandon Williams dri...@gmail.com wrote:
+1
On Thu, Aug 4, 2011 at 11:59 AM, Sylvain Lebresne sylv...@datastax.com
wrote:
As mentionned when
| 117a the square
po box 5203 | palmerston north 4441 | new zealand
P: +64 6 353 3395
E: t...@spidertracks.co.nz W: www.spidertracks.com
On Wed, 2011-08-10 at 12:26 +0200, Sylvain Lebresne wrote:
Well, this seem to be on the hector side.
I've tried the same example using the CLI
Including myself, I count 3 binding +1's, 1 other +1 and no 0s, the vote passes.
I'll get the artifacts published right away.
On Thu, Aug 11, 2011 at 9:33 AM, Eldad Yamin elda...@gmail.com wrote:
+1
On Aug 10, 2011 8:09 PM, Sylvain Lebresne sylv...@datastax.com wrote:
We just fixed a fairly
and the treatment of
aliases in Cassandra.
I think you're missing quotes. Try
comparator='DynamicCompositeType(a=AsciiType,b=BytesType,...)'. That
worked for me.
--
Sylvain
Thanks,
Todd
On Thu, 2011-08-11 at 10:57 +0200, Sylvain Lebresne wrote:
I've tried using the longer values (converted
I'm back from that beach. Eric, do you want me to do the re-roll ?
--
Sylvain
On Mon, Aug 29, 2011 at 8:28 PM, Jonathan Ellis jbel...@gmail.com wrote:
I guess we should probably re-roll; ERROR log messages tend to freak
people out even if they are innocuous.
On Sat, Aug 27, 2011 at 11:26 AM,
+1
On Fri, Sep 2, 2011 at 7:44 PM, Gary Dusbabek gdusba...@gmail.com wrote:
+1
On Wed, Aug 31, 2011 at 15:57, Eric Evans eev...@acunu.com wrote:
If at first you don't succeed[3], try, try again; I propose the
following for release as 0.7.9.
SVN:
Seems like enough awesomeness went in the 0.8 branch since 0.8.4 to warrant
a new release. I thus propose the following artifacts for release as 0.8.5.
SVN: https://svn.apache.org/repos/asf/cassandra/branches/cassandra-0.8@r1165225
Artifacts:
Ladies and Gentlemen,
It is now September 8th everywhere which means that the 1.0 freeze is now in
effect.
We are now entering the phase of heavy testing/debugging, aiming at a final
release October 8th. This means a month, which in my opinion can be done, but
only if we all focus our efforts ib
On Thu, Sep 8, 2011 at 2:51 PM, Jonathan Ellis jbel...@gmail.com wrote:
On Thu, Sep 8, 2011 at 5:14 AM, Sylvain Lebresne sylv...@datastax.com wrote:
To have things moving, I propose we aim for calling the vote on a first beta
release at the end of next week (say next Thursday for instance
It's been a week since the freeze and we don't have too many open tickets for
1.0.0. It seems like a good time to get the first beta out. Note that this is
not a release candidate yet, so the goal is more to get some wider testing, to
get bugs found sooner than later. There is a few tickets open
A few bug causing annoyance on the upgrade path have been fixed since 0.8.5, as
well as a few other improvements, so I propose the following artifacts
for release
as 0.8.6.
SVN: https://svn.apache.org/repos/asf/cassandra/branches/cassandra-0.8@r1171107
Artifacts:
I'm counting 3 binding +1's, 5 other +1's and no -1's. The vote pass.
I'll get the artifacts published.
--
Sylvain
On Thu, Sep 15, 2011 at 12:24 PM, Iroiso iro...@live.com wrote:
On 9/14/2011 9:51 PM, Vijay wrote:
+1
Regards,
/VJ
On Wed, Sep 14, 2011 at 8:56 AM, Sylvain
On Thu, Sep 15, 2011 at 11:16, Sylvain Lebresne sylv...@datastax.com
wrote:
A few bug causing annoyance on the upgrade path have been fixed since
0.8.5, as
well as a few other improvements, so I propose the following artifacts
for release
as 0.8.6.
SVN:
https://svn.apache.org/repos/asf
The first beta played its role well: bugs, small and bigger, were fixed[1].
We have no ticket left open for 1.0.0 except for a few that are minor, aren't
regressions and imho are no blocker as far as the release of 1.0.0 is
concerned. So proceeding with our plan, I think the final release is
Ok, https://issues.apache.org/jira/browse/CASSANDRA-3289 is serious enough that
we'll reroll this one. Besides,
https://issues.apache.org/jira/browse/CASSANDRA-3291 is
also nice to have in the rc2.
So this vote is closed and since both path have been committed, I'll
try to re-roll this shortly.
So the first try wasn't the right one (CASSANDRA-3289, CASSANDRA-3291) so
let's try this again.
I thus propose the following artifacts for release as 1.0.0-rc2.
SVN:
https://svn.apache.org/repos/asf/cassandra/branches/cassandra-1.0.0@r1178016
Artifacts:
The 0.8.6 has had a good run, but enough fixes were made since then to
warrant a new release of the 0.8 series. I thus propose the following
artifacts for release as 0.8.7.
SVN: https://svn.apache.org/repos/asf/cassandra/branches/cassandra-0.8@r1179171
Artifacts:
We've all been waiting for it. Apache Cassandra 1.0 is getting real folks.
All (known) blocking issues have been resolved and October 8th is there, I see
no reason to delay this any longer. I propose the following artifacts for
release as 1.0.0.
SVN:
:
+1
On Wed, Oct 5, 2011 at 9:28 AM, Jonathan Ellis jbel...@gmail.com wrote:
+1
On Wed, Oct 5, 2011 at 8:20 AM, Sylvain Lebresne sylv...@datastax.com
wrote:
The 0.8.6 has had a good run, but enough fixes were made since then to
warrant a new release of the 0.8 series. I thus propose
shortly.
--
Sylvain
On Sun, Oct 9, 2011 at 11:52 PM, Jonathan Ellis jbel...@gmail.com wrote:
+1
On Sat, Oct 8, 2011 at 6:39 AM, Sylvain Lebresne sylv...@datastax.com wrote:
We've all been waiting for it. Apache Cassandra 1.0 is getting real folks.
All (known) blocking issues have been resolved
On Mon, Oct 10, 2011 at 4:03 PM, Norman Maurer
norman.mau...@googlemail.com wrote:
Hi there,
did you alter the snappy-java version by mistake or was this part of
the commit ?
Sorry, that was intentional but I should probably not have been lazy
and made a separate commit.
I just updated the
As said while closing previous vote, CASSANDRA-3338 felt important enough to
warrant a reroll. So here it is: I propose the following artifacts for release
as 1.0.0 (those are the same as the previous + the patch for CASSANDRA-3338
and a one line fix to the build file so that it picks the right
)
at
org.apache.cassandra.service.AbstractCassandraDaemon.activate(AbstractCassa
ndraDaemon.java:337)
at
org.apache.cassandra.thrift.CassandraDaemon.main(CassandraDaemon.java:106)
Exception encountered during startup: invalid column name length 0
On 10/10/11 9:24 AM, Sylvain Lebresne sylv...@datastax.com wrote:
As said while closing
, 2011 at 11:24 AM, Sylvain Lebresne sylv...@datastax.com
wrote:
As said while closing previous vote, CASSANDRA-3338 felt important enough to
warrant a reroll. So here it is: I propose the following artifacts for
release
as 1.0.0 (those are the same as the previous + the patch for CASSANDRA-3338
Been some times since a 0.7 release with not much happening (a good thing),
but CASSANDRA-3358 is potentially silently screwing up people so it feels
worth releasing the fix. The hope is that unless something major shows up this
will be last release on the 0.7 series, crossing fingers. I thus
Because a seed_provider can be custom, you can write your own. The only
one we ship by default is the SimpleSeedProvided, but you can create your
own that say, query some service over the network to get the list of seeds.
So the parameters have to be generic for that to work and having
the
Including my own vote, I count 3 binding +1's and no -1's. The vote passes.
I'll get the artifacts published.
--
Sylvain
On Sat, Oct 29, 2011 at 2:00 AM, Eric Evans eev...@acunu.com wrote:
On Fri, Oct 28, 2011 at 4:43 AM, Sylvain Lebresne sylv...@datastax.com
wrote:
Since the final release
of the config file just for that.
--
Sylvain
On Mon, Oct 31, 2011 at 2:01 AM, Sylvain Lebresne sylv...@datastax.com
wrote:
Because a seed_provider can be custom, you can write your own. The only
one we ship by default is the SimpleSeedProvided, but you can create your
own that say, query some
12:45 PM, Sylvain Lebresne sylv...@datastax.com wrote:
Been some times since a 0.7 release with not much happening (a good thing),
but CASSANDRA-3358 is potentially silently screwing up people so it feels
worth releasing the fix. The hope is that unless something major shows up
Interesting. I've created
https://issues.apache.org/jira/browse/CASSANDRA-3434 to have a look at
it.
--
Sylvain
On Mon, Oct 31, 2011 at 6:28 PM, Jason Rutherglen
jason.rutherg...@gmail.com wrote:
...benchmarks show it as being 2x more CPU-efficient than the
equivalent pure-Java
I know 1.0.1 was just released like a week ago, but we've fixed CASSANDRA-3427
which is pretty bad. And it's not even the only thing we've fixed, so it
sounds reasonable to release 1.0.2 now (and hope it lasts longer than 1.0.1).
I thus propose the following artifacts for release as 1.0.2.
SVN:
size overflows after 2GB.)
Wouldn't that be CASSANDRA-3451? Or maybe it's me that have messed up
in the changelog, but I think that's the one and if so, it is included in the
artifacts (but we could check once jira is up again).
--
Sylvain
On Fri, Nov 4, 2011 at 7:09 AM, Sylvain Lebresne sylv
Including myself, I count 4 binding +1's and no -1's. The vote passes.
I will get the artifacts published.
Sylvain
On Sat, Nov 5, 2011 at 8:32 PM, Brandon Williams dri...@gmail.com wrote:
+1
On Fri, Nov 4, 2011 at 7:09 AM, Sylvain Lebresne sylv...@datastax.com wrote:
I know 1.0.1 was just
I know we're releasing like crazy these days, but CASSANDRA-3446 and
CASSANDRA-3482 are pretty bad and warrant a release. And then there stuffs
like CASSANDRA-3481 and a few other improvements that makes it even more worth
it.
SVN:
So, CASSANDRA-3491 and CASSANDRA-3492 got in the way of the first take.
Now that they are fixed, let's try again. I propose the following artifacts
for release as 1.0.3.
SVN: https://svn.apache.org/repos/asf/cassandra/branches/cassandra-1.0@1202082
Artifacts:
PM, Eric Evans eev...@acunu.com wrote:
On Tue, Nov 15, 2011 at 1:40 AM, Sylvain Lebresne sylv...@datastax.com
wrote:
So, CASSANDRA-3491 and CASSANDRA-3492 got in the way of the first take.
Now that they are fixed, let's try again. I propose the following artifacts
for release as 1.0.3.
SVN
of a difference to me. This would also be time consuming for me :)
(would require
a specific svn branch and whatnot).
--
Sylvain
On Tue, Nov 15, 2011 at 7:46 AM, Eric Evans eev...@acunu.com wrote:
On Tue, Nov 15, 2011 at 1:40 AM, Sylvain Lebresne sylv...@datastax.com
wrote:
So, CASSANDRA-3491
Including my own vote, I'm counting 4 binding +1's and no -1's. The vote passes.
I'll publish the artifacts shortly.
--
Sylvain
On Thu, Nov 17, 2011 at 6:53 PM, Brandon Williams dri...@gmail.com wrote:
On Thu, Nov 17, 2011 at 8:05 AM, Sylvain Lebresne sylv...@datastax.com
wrote:
Unless
I'ts been some time since we have a 0.8 release and the changelog is getting
fairly big. There's no reason to hold all those goodies from users.
I thus propose the following artifacts for release as 0.8.8.
SVN: https://svn.apache.org/repos/asf/cassandra/branches/cassandra-0.8@r1207412
Artifacts:
at 6:44 AM, Sylvain Lebresne sylv...@datastax.com
wrote:
So, 1.0.3 was not as solid as one would have hoped and CASSANDRA-3510 is
fairly bad. We've also fixed a few concurrency bugs and more, so it is
worth
pushing all this to the use now. I thus propose the following artifacts
Cassandra needs distributed regression testing. The current unit tests and
so-called 'system' tests are great, but limited in scope for a distributed
system. As pointed by others very recently, this can only help towards the
goal of having bullet-proof releases (this is obviously not enough, but
: Wednesday, November 30, 2011 11:00 AM
To: dev@cassandra.apache.org
Subject: Re: [VOTE] Release Apache Cassandra 1.0.5
+1
On Wed, Nov 30, 2011 at 10:55 AM, Eric Evans eev...@acunu.com wrote:
On Tue, Nov 29, 2011 at 1:27 PM, Sylvain Lebresne sylv...@datastax.com
wrote:
So 1.0.4 was actually
ping!
On Mon, Nov 28, 2011 at 6:09 PM, Sylvain Lebresne sylv...@datastax.com wrote:
I'ts been some time since we have a 0.8 release and the changelog is getting
fairly big. There's no reason to hold all those goodies from users.
I thus propose the following artifacts for release as 0.8.8
Including my own vote, I'm counting 3 binding +1's and no -1's. The vote passes.
I'll get the artifacts published shortly.
--
Sylvain
On Fri, Dec 2, 2011 at 3:19 PM, Jonathan Ellis jbel...@gmail.com wrote:
+1
On Mon, Nov 28, 2011 at 11:09 AM, Sylvain Lebresne sylv...@datastax.com
wrote
I know, I know, 1.0.5 is just out the oven. Yet, we've fixed a number of
annoying bugs, and in particular CASSANDRA-3551 and CASSANDRA-3577,3585
probably justify a new release by themselves. I thus propose the following
artifactfs for release as 1.0.6.
SVN:
I'm counting 4 binding +1's, one other +1 and no -1's, the vote passes.
I'll get the artifacts published.
--
Sylvain
On Sun, Dec 11, 2011 at 8:58 AM, Brandon Williams dri...@gmail.com wrote:
+1
On Sat, Dec 10, 2011 at 7:26 PM, Sylvain Lebresne sylv...@datastax.com
wrote:
I know, I know
I'm counting 3 binding +1's, 1 other +1 and no -1's. The vote passes.
I'll get the artifacts published.
On Sun, Dec 11, 2011 at 8:28 PM, Vijay vijay2...@gmail.com wrote:
+1
Regards,
/VJ
On Sat, Dec 10, 2011 at 6:10 PM, Sylvain Lebresne sylv...@datastax.comwrote:
A second vote
Ok, I think I'm warming up to what we're getting at. I would change
thesyntax of the VALUE() thing however. Instead of:CREATE TABLE
timeline ( userid int, posted_at uuid, body string, PRIMARY
KEY(user_id, posted_at), VALUE(body))I would prefer:CREATE COMPACT
TABLE timeline ( userid
This discourages collaboration because anyone that might fork
github.com/author/666 is sitting on a powder keg.
Alright, but then what is it you're proposing?
At best it's yak shaving. At worst it's going to result in some very
frustrated contributors. This is one of the major reasons why
So, I do don't like history that look like the following:
commit : last nits from reviewer commit : oops, typo that prevented
compilation commit : some more fix found during review commit :
refactor half of preceding patch following reviewer comments commit : Do
and distribution), and there is
not a single commit that looks like some nits issue from the review of a
preceding commit.
On Mon, Jan 9, 2012 at 4:38 PM, Sylvain Lebresne sylv...@datastax.com wrote:
So, I do don't like history that look like the following:
commit : last nits from reviewer commit
1 - 100 of 448 matches
Mail list logo
