On Thu, Mar 18, 2010 at 3:20 PM, Michael Malone mjmal...@gmail.com wrote:
A standard default would be nice, but while we're making recommendations
I'd also suggest that client libs should make this parameter easy to
override. Client apps can do lots of interesting things by setting
timestamps
On Fri, Apr 9, 2010 at 11:57 AM, Pablo Cuadrado pablocuadr...@gmail.comwrote:
Joseph:
Is it somehow similar to Twisted? am I wrong?
Yes, minus every protocol other than HTTP, daemonization utils, etc. Oh,
and thrift doesn't have a generator for it last I checked.
-Brandon
On Thu, Apr 15, 2010 at 9:01 AM, Eric Evans eev...@rackspace.com wrote:
We sat on 0.6.0 for a bit longer than usual in order to coordinate
with the press team, and in the meantime accumulated some important
bug fixes in the 0.6 branch. I propose we move forward with an
0.6.1 now, and get
On Tue, May 4, 2010 at 4:42 PM, Frank Du frank.d...@gmail.com wrote:
Hey All,
I updated to latest trunk code, and ran 'bin/cassandra -f'. A warning
message was spitted out:
WARN 16:42:33, 729 Couldn't detect any schema definitions in local storage.
I hope you've got a plan.
There are
On Wed, Jul 21, 2010 at 5:59 PM, Eric Evans eev...@rackspace.com wrote:
Barring objections, I'd like to tag next Tuesday July 27, and move
anything not completed by then to 0.6.5. As usual, if you have
something you think should make it in, but need more time, then let's
discuss.
+1
On Sat, Jul 24, 2010 at 9:49 PM, Jonathan Ellis jbel...@gmail.com wrote:
I propose rolling a beta release next Friday and a release candidate two
weeks
after that; anything not ready at that point can wait until 0.7.1 or 0.8.
+1
-Brandon
On Tue, Jul 27, 2010 at 5:18 PM, Eric Evans eev...@rackspace.com wrote:
As discussed last week, here is the proposed 0.6.4 release. There's
been a fair number of changes[1] since 0.6.3, so be sure to review
carefully and raise any issues you find here.
+1
-Brandon
On Tue, Aug 24, 2010 at 9:36 AM, Eric Evans eev...@rackspace.com wrote:
As I mentioned previously[3], there was an issue with the fix for the
fix to CASSANDRA-1377[3], so I propose the follow for 0.6.5. Third time
is the charm, right?
SVN:
On Wed, Sep 22, 2010 at 11:58 AM, Eric Evans eev...@rackspace.com wrote:
It feels like 0.7.0-beta1 is becoming too distant a spec in the
rear-view, and the delta[1] is becoming quite large. I propose we
vote to release a new beta.
SVN:
On Wed, Sep 22, 2010 at 4:49 PM, Brandon Williams dri...@gmail.com wrote:
-1
Before r1000136, Cassandra will refuse to start up if the machine has less
than 1G of memory.
https://issues.apache.org/jira/browse/CASSANDRA-1535 is a fairly serious
regression, as is https://issues.apache.org
On Mon, Oct 11, 2010 at 10:45 AM, Eric Evans eev...@rackspace.com wrote:
Lot's of good work[1] has made it into the 0.6 branch since 0.6.5, I
propose an 0.6.6 release.
+1
-Brandon
On Fri, Oct 22, 2010 at 3:28 AM, Chen Xinli chen.d...@gmail.com wrote:
Hi,
I'm using 0.6.6 and find hinted handoff never work.
In HintedHandOffManager.java # sendMessage(InetAddress endPoint, String
tableName, String key)
QueryFilter filter = new SliceQueryFilter(tableName, new
On Thu, Oct 28, 2010 at 9:44 AM, Gary Dusbabek gdusba...@gmail.com wrote:
+1 beta3.
+1 beta3.
-1 on committing huge changes at the end of a cycle of betas. Let's
not do that any more.
+1 on Gary's -1 to committing huge changes at the end of a cycle.
-Brandon
On Thu, Nov 4, 2010 at 1:44 PM, Jonathan Ellis jbel...@gmail.com wrote:
Apparently Eric has become a fan of Android-style release names.
Actually, I replaced HH with chocolate pudding cake. It's not any more
useful, but it tastes better.
-Brandon
On Thu, Nov 4, 2010 at 1:39 PM, Eric Evans eev...@rackspace.com wrote:
The list of changes[1] since 0.6.6 is fairly small, but there's been
some interest in getting CASSANDRA-1656[2] (a HH bug) out to people. I
propose the following for release as 0.6.7.
+1
No chance to test the brownie
On Thu, Nov 11, 2010 at 2:43 PM, Eric Evans eev...@rackspace.com wrote:
SVN:
https://svn.apache.org/repos/asf/cassandra/branches/cassandra-...@r1034097
0.6.8 artifacts: http://people.apache.org/~eevans
+1
I'd be happy to make an exception here and shorten the voting period to
expedite
On Thu, Nov 11, 2010 at 5:39 PM, Eric Evans eev...@rackspace.com wrote:
A regression caused by CASSANDRA-1622[1] (and fixed in CASSANDRA-1727[2])
made its way into the last release. With that fixed now (along with an
11th hour backport of CASSANDRA-1722[3]), I propose the following
artifacts
+1
On Sat, Nov 20, 2010 at 11:41 AM, Eric Evans eev...@rackspace.com wrote:
Barring anything unforeseen, we should be just about there. I propose
the following for release as 0.7.0 RC1.
SVN:
https://svn.apache.org/repos/asf/cassandra/branches/cassandra-...@r1037265
0.7.0-rc1 artifacts:
On Tue, Dec 14, 2010 at 6:31 PM, Rishi Bhardwaj khichri...@yahoo.comwrote:
Has anyone seen this assert failure below? Seems like a race to delete a
commit
log file. I am running 0.7-beta1, I was wondering if this has already been
fixed, in which case I can merge that fix in my current tree.
On Tue, Dec 21, 2010 at 5:39 PM, Stephen Connolly steph...@apache.orgwrote:
I have created
https://issues.apache.org/jira/browse/INFRA-3318
Can somebody on the Cassandra PMC comment on the issue and say that it's
fine for me to be driving the process
I gave it a +1
-Brandon
On Wed, Dec 22, 2010 at 11:52 AM, Kani javier.canil...@gmail.com wrote:
As a C# client maintainer, I have based Aquiles to work with Thrift than
AVRO, since there is no support for AVRO on C# yet.
Check: https://issues.apache.org/jira/browse/AVRO-533
Also, avro is more or less useless to
On Tue, Dec 21, 2010 at 7:22 PM, Eric Evans eev...@rackspace.com wrote:
We've had lots of changes[1] since RC2, too many to move to release
without wider testing. I propose the following artifacts as 0.7.0 RC3.
SVN:
https://svn.apache.org/repos/asf/cassandra/branches/cassandra-...@r1051698
On Mon, Jan 3, 2011 at 9:01 AM, Gary Dusbabek gdusba...@gmail.com wrote:
Voted and moved this discussion to a different thread.
My goal (other devs please chime in because I'm interested) would be
to still rely on ant for building and generating a pom, without the
requirement to explicitly
On Wed, Jan 5, 2011 at 3:45 PM, Jonathan Ellis jbel...@gmail.com wrote:
cassandra user and hector user lists are probably most interested.
client-dev would be good too.
-Brandon
On Thu, Jan 6, 2011 at 11:39 AM, indika kumara ind...@apache.org wrote:
*Multi-tenancy*
I noticed that you are implementing multi-tenancy [1]. Could you please
guess that how long it would take to finish to the remaining work? I would
like to contribute to that. However, I am a newbie to
+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 Yo).
SVN:
https://svn.apache.org/repos/asf/cassandra/branches/cassandra-0@r1055934
0.7.0
On Thu, Jan 6, 2011 at 12:33 PM, indika kumara indika.k...@gmail.comwrote:
Hi Brandon,
I would like you feedback on my two ideas for implementing mufti tenancy
with the existing implementation. Would those be possible to implement?
Thanks,
Indika
Two vague ideas: (1) qualified
On Mon, Jan 17, 2011 at 9:01 PM, Eric Evans eev...@rackspace.com wrote:
My opinion is we need to control the lowest layers of the code and not
rely on a third party library. By using a third party library like
Avro, it becomes a black box that we need to deeply understand and
work
On Tue, Feb 8, 2011 at 9:01 PM, Aaron Morton aa...@thelastpickle.comwrote:
I've just put the latest 0.7 build on a node and it's logging gossip
messages at DEBUG and making the logs really hard to use. Anyone object to
moving these to TRACE level ?
Moved to TRACE. I think when this was
+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
On Tue, Feb 15, 2011 at 3: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 Wed, Apr 13, 2011 at 5:13 PM, Eric Evans eev...@rackspace.com wrote:
I propose the following artifacts for release as 0.6.13.
SVN:
https://svn.apache.org/repos/asf/cassandra/branches/cassandra-0.6@r1091922
Artifacts: http://people.apache.org/~eevans
The will remain open for 72
+1
On Fri, Apr 22, 2011 at 12:17 PM, Sylvain Lebresne slebre...@apache.org 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:
On Mon, May 2, 2011 at 8:38 PM, Eric Evans eev...@rackspace.com wrote:
On Thu, 2011-04-28 at 20:42 +0100, Stephen Connolly wrote:
ok well I will see about deleting it from the staging repo, can I get
a conditional + 1 on that basis?
+1
-Brandon
+1
On May 13, 2011 4: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
+¹
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:
https://svn.apache.org/repos/asf/cassandra/branches/cassandra-0.8@r1102510
Artifacts:
+1
On Thu, May 19, 2011 at 12:42 PM, Sylvain Lebresne sylv...@datastax.com wrote:
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
I can confirm this. Third time's the charm?
-1 on this release
On Wed, May 25, 2011 at 8:50 PM, Shotaro Kamio kamios...@gmail.com wrote:
Just looking at a patch, but CASSANDRA-2626 fix may not be right.
I'll check within a day.
Regards,
Shotaro
On Thu, May 26, 2011 at 6:05 AM, Eric
+1
On Mon, May 30, 2011 at 2:04 PM, Eric Evans eev...@rackspace.com wrote:
OK, let's try this yet again; I propose the following artifacts for release
as 0.8.0 (final).
SVN:
https://svn.apache.org/repos/asf/cassandra/branches/cassandra-0.8.0@r1129278
Artifacts:
On Tue, May 31, 2011 at 5:16 PM, Edward Capriolo edlinuxg...@gmail.com wrote:
@Jeremy is this just because Pig's output does not use the OutputFormat?
It does use it, but we specifically fixed pig and probably forgot to
fix the word count.
It could be significant because the OutputFormat was
+1
On Thu, Jul 7, 2011 at 10:14 AM, 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:
for following up, Jim.
On Mon, Jul 18, 2011 at 2:57 PM, Brandon Williams dri...@gmail.com wrote:
You should mark it 'patch available' so someone will know to review it.
On Mon, Jul 18, 2011 at 2:55 PM, Jim Ancona j...@anconafamily.com wrote:
I attached a patch to CASSANDRA-2717 a week or so ago
+1
-Brandon
On Thu, Jul 21, 2011 at 10:11 AM, Sylvain Lebresne sylv...@datastax.com wrote:
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
+1
On Fri, Jul 22, 2011 at 4: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 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
Please test removetoken thoroughly for this release,
https://issues.apache.org/jira/browse/CASSANDRA-2496 was a significant
change that completely reworked the existing (broken) behavior.
-Brandon
On Tue, Aug 2, 2011 at 1:28 PM, Sylvain Lebresne sylv...@datastax.com wrote:
We have found and
+1
On Thu, Aug 4, 2011 at 11:59 AM, Sylvain Lebresne sylv...@datastax.com wrote:
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
+1
On Wed, Aug 10, 2011 at 12:08 PM, Sylvain Lebresne sylv...@datastax.com wrote:
We just fixed a fairly serious bug with counter (CASSANDRA-3006 -- it is
serious in that it corrupt counters). Cassandra 0.8.3 also shipped with a
potential small upgrade problem (CASSANDRA-3011). There is no
+1
On Mon, Sep 5, 2011 at 6:25 AM, Sylvain Lebresne sylv...@datastax.com wrote:
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:
On Mon, Sep 12, 2011 at 12:35 AM, Tharindu Mathew mcclou...@gmail.com wrote:
Hi,
I plan to do $subject and contribute.
Right now, the hadoop integration splits according to the number of rows in
a slice predicate. This doesn't scale if a row has a large number of
columns.
I'd like to know
+1
On Wed, Sep 14, 2011 at 10:56 AM, Sylvain Lebresne sylv...@datastax.com wrote:
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
On 9/23/11, Todd Burruss bburr...@expedia.com wrote:
INFO [HintedHandoff:4] 2011-09-22 22:59:27,626 HintedHandOffManager.java
(line 259) Started hinted handoff for token:
150124573641590498586782915043427152112 with IP: /10.185.35.39
ERROR [HintedHandoff:4] 2011-09-22 22:59:27,648
On Fri, Sep 23, 2011 at 6:00 PM, Todd Burruss bburr...@expedia.com wrote:
Here is a sample from one of the machines:
Pool Name Active Pending Completed Blocked All time blocked
MutationStage 32 1492 1416296 0 0
Can you get a thread dump to see
On Sun, Sep 25, 2011 at 5:43 PM, Radim Kolar h...@sendmail.cz wrote:
Cassandra binary distribution contains avro-1.4.0-sources-fixes.jar which is
source code jar. It is packaged by mistake?
No, it is (unfortunately) used for schema migrations.
-Brandon
+1
On Mon, Sep 26, 2011 at 7:37 AM, Sylvain Lebresne sylv...@datastax.com wrote:
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
+1
On Sat, Oct 1, 2011 at 12:13 PM, Jonathan Ellis jbel...@gmail.com wrote:
+1
On Sat, Oct 1, 2011 at 11:25 AM, Sylvain Lebresne sylv...@datastax.com
wrote:
So the first try wasn't the right one (CASSANDRA-3289, CASSANDRA-3291) so
let's try this again.
I thus propose the following
+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 the
On Tue, Oct 11, 2011 at 8:29 AM, Sylvain Lebresne sylv...@datastax.com wrote:
So I have created new artifacts, based on the previous ones but with the
infamous 'echo $CLASSPATH' removed from cassandra.in.sh. And what I'm
proposing is to simply switch to those last artifacts for the release
On Mon, Oct 10, 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
On Tue, Oct 11, 2011 at 10:26 AM, Sylvain Lebresne sylv...@datastax.com wrote:
Let's hope third times will be the charm. With #3343, #3345 and #3346 in, I
propose the following artifacts for release as 1.0.0.
SVN:
https://svn.apache.org/repos/asf/cassandra/branches/cassandra-1.0.0@r1181820
+1
On Oct 28, 2011 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
+1
On Fri, Nov 11, 2011 at 3:50 PM, Sylvain Lebresne sylv...@datastax.com wrote:
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
On Thu, Nov 17, 2011 at 8:05 AM, Sylvain Lebresne sylv...@datastax.com wrote:
Unless someone object strongly I'm probably going to be lazy and not rebuild
the
artifacts to reflect the correct api. My own justification for my
laziness is that I
don't want to get into the habit of releasing
+1
On Sat, Dec 10, 2011 at 8:10 PM, Sylvain Lebresne sylv...@datastax.com wrote:
A second vote in the same day!? I know what you've just though: santa comes
early this year. But no, you're not dreaming: CASSANDRA-3472 (0.8.8)
re-enabled cross-DC efficient writes that was mistakenly disabled
On Sat, Dec 17, 2011 at 12:09 PM, Piotr Kołaczkowski
pkola...@ii.pw.edu.pl wrote:
A patch for the (rare) problem I've found just by accidentally reading the
code.
Can you attach it to https://issues.apache.org/jira/browse/CASSANDRA-3615 ?
Thanks!
-Brandon
On Mon, Dec 19, 2011 at 1:19 AM, 夏帆 xiafa...@gmail.com wrote:
Recently I try to find out when a bootstraping node jumps from
joinning state to normal. I read the source code related to bootstrap and
have not found the codes updating the state of the node to be normal. In
On Mon, Dec 19, 2011 at 7:59 PM, 夏帆 xiafa...@gmail.com wrote:
StorageService.joinTokenRing will only execute bootstrap(token) if the node
boostraps. setToken is executed during a non-bootstrap startup.
Right. bootstrap(token) is only called for bootstrapping nodes, but
setToken is called
On Tue, Dec 20, 2011 at 12:45 AM, Radim Kolar h...@sendmail.cz wrote:
can you make release cycle slower? its better to have more new features and
do major upgrades less often. it saves time needed for testing and
migrations.
http://www.mail-archive.com/dev@cassandra.apache.org/msg01549.html
On Tue, Jan 10, 2012 at 2:59 PM, Jonathan Ellis jbel...@gmail.com wrote:
I've tagged 7 tickets as critical [1] for 1.1. All of them deal
with CQL;
Actually 1391 doesn't, but is quite important nonetheless.
All of these (with the exception of 3707, which is relatively quick)
are in progress,
On Tue, Jan 10, 2012 at 11:40 PM, Dave Brosius dbros...@mebigfatguy.com wrote:
Greetings,
I wanted to mention this to folks who may be running into this issue. A
user on IRC reporting that cloning the cassandra repo on the apache servers
http://git-wip-us.apache.org/repos/asf/cassandra.git
+1
On Fri, Jan 13, 2012 at 3:44 AM, Sylvain Lebresne sylv...@datastax.com wrote:
With the fix for CASSANDRA-3733 and CASSANDRA-3625 added on top of the
artifacts of Strike 1, I propose the following artifacts for release as 1.0.7
Sha1: 6a1ed6205cad8d019eb6eda326d7796a8a0dd67b
Git:
On Mon, Jan 30, 2012 at 6:36 PM, aaron morton aa...@thelastpickle.com wrote:
p.s. the user list is the appropriate list for emails like this.
I disagree, this was on-topic for dev@ imho.
-Brandon
On Mon, Jan 30, 2012 at 6:42 PM, aaron morton aa...@thelastpickle.com wrote:
Sorry, i thought bug reports went to the user list.
Well, if it was just I have this exception then sure, but Dave has
done quite a few patches and dug into the problem pretty specifically
and was asking if it's a big
+1
On Wed, Feb 8, 2012 at 10:19 AM, Sylvain Lebresne sylv...@datastax.com wrote:
It's been close to 2 months since 0.8.9 and while things are mostly calm on
the 0.8 branch, we do have a few fixes in there that is worth releasing.
I thus propose the following artifacts for release as 0.8.10.
+1
On Thu, Feb 16, 2012 at 8:07 AM, Jonathan Ellis jbel...@gmail.com wrote:
+1
On Thu, Feb 16, 2012 at 4:36 AM, Sylvain Lebresne sylv...@datastax.com
wrote:
The 1.1.0 freeze has been going on for more than 2 weeks now, with not that
many big issues so far. I think it is time to release a
+1
On Wed, Feb 22, 2012 at 8:57 AM, Sylvain Lebresne sylv...@datastax.com wrote:
Been some time since 1.0.7 and bugs have been fixed, I thus propose the
following artifacts for release as 1.0.8.
sha1: fe6980eb7d2df6cb53fd8a83226f91789beaced8
Git:
+1
On Fri, Mar 23, 2012 at 5:26 AM, Sylvain Lebresne sylv...@datastax.com wrote:
There is has been quite some changes since the beta1[1] (including some non
trivial ones) and so while we still have a few outstanding small issues that
may need to be addressed before calling for a release
+1
On Tue, Apr 3, 2012 at 10:21 AM, Sylvain Lebresne sylv...@datastax.com wrote:
The first attempt was closed to include the fix for CASSANDRA-4112. After have
committed said fix, I'm proposing the following artifacts for release as
1.0.9.
sha1: 3fd0fb6aa0038f0c8aaf34f98f2ceed2f308a501
Try nosetests -ve to see which one is failing and exit on the first error.
On Apr 14, 2012 1:34 PM, Mark Dewey milde...@gmail.com wrote:
I thought I followed the instructions to set up the nose tests, but when I
run them all they do is (slowly) print out .E and then hang. Any clues?
Mark
+1
On Fri, Apr 20, 2012 at 12:38 PM, Sylvain Lebresne sylv...@datastax.com wrote:
The RC1 went well and we basically don't have any issue open left, so I
think it's time to release the final Cassandra 1.1. I thus propose the
following artifacts for release as 1.1.0.
sha1:
I am very +1 on this. I think Cassandra has matured to a point that
warrants this.
On Fri, Apr 20, 2012 at 12:57 PM, Jonathan Ellis jbel...@gmail.com wrote:
After the 0.7 release we decided to shoot for a fixed four-month
release cycle. I think now is a good time to re-evaluate this, and
+1
On Fri, May 4, 2012 at 11:33 AM, Sylvain Lebresne sylv...@datastax.com wrote:
It's been a month since 1.0.9 and CASSANDRA-4116 is kind of a big deal so I
propose the following artifacts for release as 1.0.10.
sha1: b2ca7f82122325f1fe83478e6609d71805dcfc84
Git:
On Tue, May 15, 2012 at 3:23 PM, Vladimir Vivien
vladimir.viv...@gmail.com wrote:
Is there any plan to modularize cassandra codebase ?
There are tons of subsystems within cassandra begging to be reused
elsewhere.
For instance, the implementation of gossip and countless other examples
that
+1
On Fri, Jun 1, 2012 at 1:21 PM, Sylvain Lebresne sylv...@datastax.com wrote:
We've have fixed tons of bugs since 1.1.0 and have nothing critical
outstanding
so I propose the following artifacts for release as 1.1.1.
sha1: a788a23ca6fbb03f991a0c54325c371b4b1dd7cf
Git:
+1
On Jun 29, 2012 11:21 AM, Sylvain Lebresne sylv...@datastax.com wrote:
We've fixed a fair amount of issues so I believe it is time for a new
release
and thus propose the following artifacts for release as 1.1.2.
sha1: b94d8d40fb6f84b4041857bf69ddf7cd22df2e86
Git:
+1
On Fri, Jul 27, 2012 at 11:38 AM, Sylvain Lebresne sylv...@datastax.com wrote:
The 1.0 branch is fairly stable now but we still have fixed a few bugs since
1.0.10 so I propose the following artifacts for release as 1.0.11.
sha1: 4f0237acd5ee8097f90732ac416622588e4d7552
Git:
On Mon, Jul 30, 2012 at 9:52 AM, Jonathan Ellis jbel...@gmail.com wrote:
Is Jenkins smart enough to be able to say, I know we had X findbugs
warnings previously, which are known to be false positives, but now
there are X+1 ?
In my experience, jenkins hasn't even been smart enough to build
On Tue, Jul 31, 2012 at 5:23 AM, Sylvain Lebresne sylv...@datastax.com wrote:
Some fair amount of bug have been fixed since 1.1.2, including a few important
ones, so I propose the following artifacts for release as 1.1.3.
It looks like we need to get
Oops, can we also add the small fix from
https://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=commitdiff;h=6dfb3a8557a39ac22dccbf3c597f558d310fb7e8
?
On Wed, Aug 1, 2012 at 1:29 PM, Sylvain Lebresne sylv...@datastax.com wrote:
Let's try that again. I propose the following artifacts for
+1
On Thu, Aug 2, 2012 at 1:43 AM, Sylvain Lebresne sylv...@datastax.com wrote:
Hopefully for the last time I propose the following artifacts for
release as 1.1.3.
sha1: 94bcc6a6f6171796e3147dec73d71df05c370f94
Git:
+1
On Tue, Aug 14, 2012 at 4:34 PM, Eric Evans eev...@acunu.com wrote:
I knew I'd mess up something; So here we go again, this time built
with the right version of JDK.
SHA1: 8b1336f
Git:
http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/1.1.4-tentative
+1
On Fri, Sep 7, 2012 at 12:37 PM, Sylvain Lebresne sylv...@datastax.com wrote:
The fix to #4561 have now been pushed and we even have a few more fixes
committed since the first try and so let's try again: I propose the following
artifacts for release as 1.1.5.
sha1:
+1
The vnode troubleshooting process has been rough, so I'm all for more
testing there.
On Tue, Sep 25, 2012 at 12:16 PM, Jonathan Ellis jbel...@gmail.com wrote:
We are more or less on track for the promised late October 1.2 release
[1] but I'm starting to think we should expand the scope of
On Tue, Oct 2, 2012 at 4:52 AM, Niteesh kumar nitees...@directi.com wrote:
while looking at netstat table i observed that my cluster nodes not using
persistent connection to talk among themselves on port 9160 to redirect
request.
9160 is the thrift port. This basically means your client
On Thu, Oct 4, 2012 at 1:25 PM, Kirk True k...@mustardgrain.com wrote:
Hi all,
Test scenario:
4 nodes (.1, .2, .3, .4)
RF=3
CL=QUORUM
1.1.2
I noticed that in ReadCallback's constructor, it determines the 'blockfor'
number of 2 for RF=3, CL=QUORUM.
Which is correct.
Check for a stacktrace in the server log.
On Mon, Oct 8, 2012 at 9:18 PM, Vivek Mishra vivek.mis...@yahoo.com wrote:
Hi All,
I am trying to use compound primary key column name and i am referring to:
http://www.datastax.com/dev/blog/whats-new-in-cql-3-0
As mentioned on this example, i
On Wed, Oct 10, 2012 at 3:54 AM, Alexey Zotov azo...@griddynamics.com wrote:
Are there some another tests, except included to the project? If no, then I
suggest to create pack of integration tests based on ccm. It requires
additional writing of scripts for more deep configuration and management
+1
On Fri, Oct 12, 2012 at 9:17 AM, Sylvain Lebresne sylv...@datastax.com wrote:
Ladies and gentlemen, with now added fix for leveled compaction and for
CASSANDRA-4782, I propose the following artifacts for release as
1.1.6
sha1: a0900f3d3b9fadc3608bc6c4960ed1858d581e13
Git:
+1
On Mon, Nov 5, 2012 at 1:08 PM, Sylvain Lebresne sylv...@datastax.com wrote:
Lots have happened since beta1 and it's time to think seriously about the
1.2.0
release, so I propose the following artifacts for release as
1.2.0-beta2.
sha1: f04bebfa7e5fb0efd003685b10c0e31250de441d
Git:
+1
On Tue, Nov 27, 2012 at 3:29 AM, Sylvain Lebresne sylv...@datastax.com wrote:
A fair amount of fixes went in since 1.1.6, so I propose the following
artifacts for release as 1.1.7.
sha1: 2f4b6d8c61d81ac4c878a4399a3634221deeb075
Git:
On Sat, Dec 1, 2012 at 12:24 PM, Edward Capriolo edlinuxg...@gmail.com wrote:
I do not understand why everyone wants to force this issue on removing
thrift.
I'm -1 on removing thrift, and by my count, that would put us at -3
binding if it ever came to vote, so let's consider this proposition
1 - 100 of 702 matches
Mail list logo
