+1
On Tue, Aug 14, 2012 at 4:34 PM, Eric Evans 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
> Artifacts:
> htt
+1
On Fri, Sep 7, 2012 at 12:37 PM, Sylvain Lebresne 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: e395307893d93a01e976656f6e0f5cee1acf3c3
+1
On Tue, Sep 18, 2012 at 11:55 AM, Sylvain Lebresne wrote:
> If we want to stay true to our new 6 months release cycle we should start
> getting serious about the release of 1.2. For that, it would definitively help
> to get wider testing and besides, all the issues marked 1.2.0-beta1 on JIRA
+1
On Mon, Sep 24, 2012 at 4:52 PM, Sylvain Lebresne wrote:
> We've just fixed CASSANDRA-4708 and have a few other minor fixes on the 1.0
> branch since 1.0.11 so I propose the following artifacts for release as
> 1.0.12.
>
> sha1: 373e5b0d5104f17fca77edafbc033da99bced64c
> Git:
> http://git-wi
+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 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 1.2 a bit
> to ge
On Tue, Oct 2, 2012 at 4:52 AM, Niteesh kumar 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 sucks if
it's not pooli
On Thu, Oct 4, 2012 at 1:25 PM, Kirk True 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. floor(3/2) = 1
Check for a stacktrace in the server log.
On Mon, Oct 8, 2012 at 9:18 PM, Vivek Mishra 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 tried to create a co
On Wed, Oct 10, 2012 at 3:54 AM, Alexey Zotov 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 of
> ccm's cluster.
+1
On Fri, Oct 12, 2012 at 9:17 AM, Sylvain Lebresne 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:
> http://git-wip-us.apache.or
+1
On Mon, Nov 5, 2012 at 1:08 PM, Sylvain Lebresne 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:
> http://git-wip-u
+1
On Tue, Nov 27, 2012 at 3:29 AM, Sylvain Lebresne 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:
> http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=re
On Sat, Dec 1, 2012 at 12:24 PM, Edward Capriolo 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
closed and move on to
On Fri, Nov 30, 2012 at 4:17 AM, Sylvain Lebresne wrote:
> We've fixed pretty much all know issues since beta2 (remains 2 issues tagged
> 1.2.0 but none are really critical if they don't make it anyway) so so I
> propose the following artifacts for release as 1.2.0-rc1.
I think we should solve CA
On Sun, Dec 2, 2012 at 10:45 PM, Jonathan Ellis wrote:
> I'm not a fan of blocking a new rc because of bugs that are not
> regressions new in that release. I'd also like to get more testing on
> the 1.2 fixes since b2. But we can call it b3 instead of rc1 if you
> want.
I agree with everything
+1
On Mon, Dec 3, 2012 at 12:43 PM, Sylvain Lebresne wrote:
> So it seems we have a few things to fix before calling it a proper release
> candidate, but we still have had quite a bit of changes since beta2 so I
> propose the following artifacts for release as 1.2.0-beta3.
>
> sha1: b86f75dcd7041
+1
On Tue, Dec 11, 2012 at 11:42 AM, Pavel Yaskevich wrote:
> +1
>
> On Tuesday, December 11, 2012 at 8:28 AM, Yuki Morishita wrote:
>
>> +1
>>
>> yuki
>>
>>
>> On Tuesday, December 11, 2012 at 7:27 AM, Jonathan Ellis wrote:
>>
>> > +1
>> > On Dec 11, 2012 5:19 AM, "Sylvain Lebresne" > > (mailto:
+1
On Mon, Dec 17, 2012 at 3:28 AM, Sylvain Lebresne wrote:
> We've fixed a few annoying issue since 1.1.7 so I propose the following
> artifacts for release as 1.1.8.
>
> sha1: 4885bfccf1841def0c86b46302133cf2924d7acd
> Git:
> http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=r
+1
On Dec 20, 2012 4:58 AM, "Sylvain Lebresne" wrote:
> There was a few quacks with rc1 (most notably #5064) but we've fixed those,
> so I propose
> the following artifacts for release as 1.2.0-rc2. Hopefully the final
> should come quickly after that one.
>
> sha1: cfe51fb4f7aeddd424525b59451e71
On Sat, Jan 5, 2013 at 12:20 AM, Jason Brown wrote:
> I'm worried about terminating a node and it's hints never getting played
> before it disappears. Node repair, of course, would help on the
> anti-entropy front, but wondering if there's value in streaming the hints
> to a peer (in the same rack
On Tue, Jan 8, 2013 at 6:10 PM, Jonathan Ellis wrote:
> I agree, the Syn doesn't contain any EndpointState information and
> notifyFD on the local state doesn't look useful.
>
> What do you think Brandon, can we just get rid of that call and the
> nFD overload it invokes?
Probably, since the real
On Wed, Jan 9, 2013 at 9:21 AM, Radim Kolar wrote:
> removing max_compaction_threshold in 1.2 was bad move, keeping it low helps
> compaction throughput because it lowers number of disk seeks.
:(
On Wed, Jan 9, 2013 at 9:40 AM, Edward Capriolo wrote:
> :( Seems like a good thing to have, i can figure at least one degenerate
> scenario where having that helps. The first being a currupt sstable...
> compaction will never be able to remove it and then each compaction will
> likely try to coma
+1
On Mon, Jan 14, 2013 at 1:36 PM, Sylvain Lebresne wrote:
> We've fixed our fair share of bugs since 1.1.8 so I propose the following
> artifacts for release as 1.1.9.
>
> sha1: 7eb47c50c394f0aefdfd4ac9170ce51e2e4be549
> Git:
> http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h
On Tue, Jan 15, 2013 at 8:19 AM, Jason Brown wrote:
> Is it possible to add CASANDRA-5155 to 1.1.9? The patch and it's impact is
> rather small. Otherwise, +1
If this is something you _really_ wanted, since snitches are
pluggable, you could take the patched version and rename it to avoid
conflict
+1
On Fri, Jan 25, 2013 at 1:53 AM, Sylvain Lebresne wrote:
> That list of changes since 1.2.0 is getting pretty long, time to ship that
> to
> users. I propose the following artifacts for release as 1.2.1.
>
> sha1: 8540974dbd26989b1cd72608b06e57ebe053bf38
> Git:
> http://git-wip-us.apache.org/r
On Mon, Feb 4, 2013 at 2:11 PM, William Katsak wrote:
> Hello,
>
> I am working on some modifications of Cassandra in an academic setting
> (research code, not for a class), and have a question regarding bulk
> streaming of data across the network (e.g. between nodes).
>
> Assume that I have some
On Wed, Feb 6, 2013 at 4:21 PM, Jonathan Ellis wrote:
> Java 6 EOL is this month. Java 7 will be two years old when C* 2.0
> comes out (July). Anecdotally, a bunch of people are running C* on
> Java7 with no issues, except for the Snappy-on-OS-X problem (which
> will be moot if LZ4 becomes our d
+1
On Tue, Feb 12, 2013 at 3:59 AM, Sylvain Lebresne wrote:
> We've fixed our share of bugs since 1.1.9 so I propose the following
> artifacts
> for release as 1.1.10.
>
> sha1: 684994215120b2bac4e04f520420e105e21d07c9
> Git:
> http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=r
On Wed, Feb 13, 2013 at 11:26 AM, Jonathan Ellis wrote:
> The Apache Cassandra PMC has voted to add Jason as a committer.
> We look forward to making Cassandra better together!
Congrats, Jason!
-Brandon
On Wed, Feb 13, 2013 at 1:18 PM, Vladimir Vivien
wrote:
> How does one get that committer badge?
Contribution, and time.
-Brandon
On Wed, Feb 13, 2013 at 1:27 PM, Vladimir Vivien
wrote:
> Is this http://wiki.apache.org/cassandra/HowToContribute still the best
> place to get started?
Yes, still looks fairly accurate to me.
-Brandon
+1
On Feb 20, 2013 4:01 PM, "Sylvain Lebresne" wrote:
> We've fixed a fair amount of important fixes since 1.2.1 so I propose the
> following artifacts for release as 1.2.2.
>
> sha1: 068b53dd5de928fd80815b54963af796f51f1c38
> Git:
>
> http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shor
On Mon, Feb 25, 2013 at 5:19 PM, Edward Capriolo wrote:
> I am curious what you mean when you say "does the fat client work right
> now?"
It's not often tested.
> What does not work about it? I have a fat client app running same jvm as c*
> it seems to work well.
Good to know. :)
-Brandon
+1
On Thu, Mar 14, 2013 at 5:04 AM, Sylvain Lebresne wrote:
> Some important bug fixed since 1.2.2, I propose the following artifacts for
> release as 1.2.3.
>
> sha1: f07804e0d0cf57bc6e1e2924a7b926d55408f640
> Git:
> http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/1
On Mon, Apr 8, 2013 at 12:54 PM, Sylvain Lebresne wrote:
> A fair enough number of bugs fixed since 1.2.3, I propose the following
> artifacts for release as 1.2.4.
>
> sha1: 2e96d07114dc88f85e56d88f7322a6b91da36c0d
>
+1
On Wed, Apr 10, 2013 at 9:50 PM, Carl Yeksigian wrote:
> This discussion is off topic for the dev list. If you want to continue it,
> please move to user@.
>
I disagree entirely, this is absolutely dev-oriented.
-Brandon
+1
On Apr 16, 2013 8:59 PM, "Eric Evans" wrote:
>
> Greets,
>
> I propose the following for release as 1.1.11
>
> SHA1: d939a0c958d36a3debfc63364a3fa569aa632c6e
> Git:
> http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/1.1.11-tentative
> Artifacts:
> https://repositor
I'd like to see https://issues.apache.org/jira/browse/CASSANDRA-5432 get in
first. Vijay, can you commit?
On Fri, May 3, 2013 at 1:21 PM, Sylvain Lebresne wrote:
> A fair enough number of bugs fixed since 1.2.4, I propose the following
> artifacts for release as 1.2.5.
>
> sha1: de98541708b9a59e
+1
On Mon, May 6, 2013 at 3:15 AM, Sylvain Lebresne wrote:
> Now that the offending tickets have been committed (#5432 and #5535), let's
> re-roll this. So I propose the following artifacts for release as 1.2.5.
>
> sha1: 59bd0e7169c5fabc0e734ccbbbcd6964709577d0
> Git:
>
> http://git-wip-us.apach
+1
On Wed, May 15, 2013 at 9:16 AM, Sylvain Lebresne wrote:
> Hopefully third times the charm. The #4860 fix has been committed so I
> propose
> the following artifacts for release as 1.2.5.
>
> sha1: 7d4380d661e7bbf3ec075b069cf2c22e9b87375f
> Git:
>
> http://git-wip-us.apache.org/repos/asf?p=cas
+1
On Tue, May 21, 2013 at 1:59 PM, Jonathan Ellis wrote:
> CHANGES:
> * Remove buggy thrift max message length option (CASSANDRA-5529)
> * Add retry mechanism to OTC for non-droppable_verbs (CASSANDRA-5393)
> * Use allocator information to improve memtable memory usage estimate
>(CASSAND
Hate to say it, but let's re-roll for 5488 round two. I don't see a 1.1.13
ever happening, so it'd be good to get 1.1.12 as correct as possible.
On Wed, May 22, 2013 at 4:06 AM, Sylvain Lebresne wrote:
> I propose the following artifacts for release as 1.1.12.
>
> sha1: 0db94069550b9c38b9f749e20
+1
On Thu, May 23, 2013 at 3:03 AM, Sylvain Lebresne wrote:
> I propose the following artifacts for release as 1.1.12 (now with more
> #5488 fixes inside).
>
> sha1: 2dd73d171068d743befcd445a14751032d232e4e
> Git:
>
> http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/1
+1
On Fri, Jun 21, 2013 at 12:46 PM, Sylvain Lebresne wrote:
> It's ample time for a new minor release on 1.2. I propose the following
> artifacts for
> release as 1.2.6.
>
> sha1: 79410e4a887e7adac796339c1a565436deaf254a
> Git:
>
> http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlo
Actually, -1, we'll need a re-roll:
http://buildbot.datastax.com:8010/builders/cassandra-1.2/builds/503
On Fri, Jun 21, 2013 at 12:46 PM, Sylvain Lebresne wrote:
> It's ample time for a new minor release on 1.2. I propose the following
> artifacts for
> release as 1.2.6.
>
> sha1: 79410e4a887e7ad
+1
On Sat, Jun 22, 2013 at 5:46 AM, Sylvain Lebresne wrote:
> The previous assertion error has been fix so I propose the following
> artifacts
> for release as 1.2.6.
>
> sha1: 043a63c63b92b0bf68047da6b5e379da35f3c688
> Git:
>
> http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=
+1
On Tue, Jun 25, 2013 at 3:41 AM, Sylvain Lebresne wrote:
> After having reverted CASSANDRA-5665, I propose the following artifacts for
> release as 1.2.6.
>
> sha1: a6ca5d496facf79c187310e81b3eeba3e6bc4b43
> Git:
>
> http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags
+1
On Tue, Jul 9, 2013 at 4:20 AM, Sylvain Lebresne wrote:
> Cassandra 2.0 is coming along but we now need wider testing. So I propose
> the
> following artifacts for release as 2.0.0-beta1. Let it be clear that it is
> only
> a beta (and the first one at that), so we know it's not perfect, but t
On Wed, Jul 17, 2013 at 3:18 PM, Vladimir Prudnikov
wrote:
> I read somewhere that it will be for backward compatibility, but does it
> mean that new features
> will not be added to the Thrift interface
Yes, the thrift interface will remain stable and not be changing.
-Brandon
+1
On Tue, Jul 23, 2013 at 9:27 AM, Sylvain Lebresne wrote:
> Quite a few bugs fixed since 1.2.6, I propose the following artifacts for
> release as 1.2.7.
>
> sha1: ae62c947fc245295785324502bf6bc2c1c8477f9
> Git:
>
> http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/1
+1
On Wed, Jul 24, 2013 at 11:21 AM, Sylvain Lebresne wrote:
> So, now with some CASSANDRA-5799 inside, I propose the following artifacts
> for
> release as 1.2.7.
>
> sha1: ce4e4b9b5b29b0e0518aafe02544de3765ea9dd7
> Git:
>
> http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=ref
On Sat, Jul 27, 2013 at 2:39 PM, Jonathan Ellis wrote:
> The fix for range tombstone performance [1] introduced a regression
> [2] that breaks slice queries against 1.1-format sstables. Running
> upgradesstables is a workaround, but this means that you can't do
> zero-downtime upgrades from 1.1
+1
On Sat, Jul 27, 2013 at 8:15 PM, Eric Evans wrote:
>
> A regression made its way into 1.2.7 and has since been fixed [2]; I
> propose the following artifacts for release as 1.2.8.
>
> Git SHA1: 0291d696018214000709025c0b806089c2f51e97
> Git HTTP:
> http://git-wip-us.apache.org/repos/asf?p=cas
+1
On Mon, Aug 5, 2013 at 11:54 AM, Eric Evans wrote:
>
> Sounds like it's that time; I propose the following artifacts for
> release as 2.0.0 rc1.
>
> Git: 2.0.0-rc1-tentative / e8ae672
> Gitweb:
> https://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=commit;h=e8ae672
> Artifacts:
> https:/
On Wed, Aug 7, 2013 at 12:55 AM, Kasper Nielsen wrote:
> Hi,
>
> I was wondering if there are any other reasons than licensing for why JNA
> is not included in the distribution.
> As of JNA 4.0.0 (released last month) it is available under a dual LGPL APL
> 2.0 license.
>
Licensing has been the
If you're using ccm this can happen. Make a conf/triggers directory and
that will fix it. We fixed this in trunk already.
On Aug 10, 2013 1:31 PM, "Radim Kolar" wrote:
> did you package it correctly? something seems to be missing
>
> ERROR 20:27:11,578 Internal error processing batch_mutate
> jav
On Sun, Aug 11, 2013 at 9:35 PM, Jonathan Ellis wrote:
> We hadn't actually set vnodes to be on by default, which we should do
> after having 1.2 default to old single token per node. Fixed in
> CASSANDRA-5869 so let's roll an rc2.
>
>
Let's get https://issues.apache.org/jira/browse/CASSANDRA-5
+1
On Aug 17, 2013 8:15 PM, "Jonathan Ellis" wrote:
> Added a short description.
>
> On Mon, Aug 12, 2013 at 12:40 AM, Dave Brosius
> wrote:
> > On 08/11/2013 10:51 PM, Brandon Williams wrote:
> >>
> >> On Sun, Aug 11, 2013 at 9:35 PM, Jonathan Ell
+1
On Mon, Aug 19, 2013 at 11:15 AM, Sylvain Lebresne wrote:
> As mention by Jonathan in a previous email, we're now ready for a 2nd RC,
> so
> here it is, I propose the following artifacts for release as 2.0.0-rc2.
>
> sha1: 3e516a3287606421a3f400e801bb429029b5598c
> Git:
>
> http://git-wip-us.
+1
On Mon, Aug 26, 2013 at 1:53 PM, Sylvain Lebresne wrote:
> The changelog is getting big, I propose the following artifacts for release
> as 1.2.9.
>
> sha1: ae62c947fc245295785324502bf6bc2c1c8477f9
> Git:
>
> http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/1.2.9-
+1
On Wed, Aug 28, 2013 at 9:13 AM, Sylvain Lebresne wrote:
> The RC2 period has been relatively calm so far and in term of timing, we're
> way
> late on our "regular 6 month schedule". It's time to release that final and
> thus I propose the following artifacts for release as 2.0.0.
>
> sha1: 0
+1
On Thu, Sep 19, 2013 at 5:59 AM, Sylvain Lebresne wrote:
> The changelog is getting big, I propose the following artifacts for release
> as 1.2.10.
>
> sha1: 937536363a8a6d86ee32fe5ef90653264e67b6c7
> Git:
>
> http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/1.2.1
+1
On Tue, Oct 15, 2013 at 3:36 AM, Sylvain Lebresne wrote:
> The changelog is getting big, I propose the following artifacts for release
> as 1.2.11.
>
> sha1: 6165840f1584f932064b8ad2320b29de632ed813
> Git:
>
> http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/1.2.1
Changed my mind :(
https://issues.apache.org/jira/browse/CASSANDRA-6208
On Wed, Oct 16, 2013 at 7:39 AM, Brandon Williams wrote:
> +1
>
>
> On Tue, Oct 15, 2013 at 3:36 AM, Sylvain Lebresne wrote:
>
>> The changelog is getting big, I propose the following artifacts for
&g
+1
On Fri, Oct 18, 2013 at 11:38 AM, Sylvain Lebresne wrote:
> With CASSANDRA-6208 now fixed, I propose the following artifacts for
> release
> as 1.2.11.
>
> sha1: 9424449716ac4adf7e8ee698c14ac5dfccc4e7d6
> Git:
>
> http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/1
Sure, we just need to know your wiki account name (make an account if you
don't have one.)
On Tue, Oct 22, 2013 at 11:13 AM, ono_matope wrote:
> Hi, Cassandra guys!
>
> I'm a software engineer who work with Cassandra in Japan.
>
> I would like to participate in the translation of Cassandra wiki
Added.
On Tue, Oct 22, 2013 at 11:18 AM, ono_matope wrote:
> Oh sorry. My account name is "ono_matope".
>
> On 2013/10/23, at 1:16, Brandon Williams wrote:
>
> > Sure, we just need to know your wiki account name (make an account if you
> > don't have on
+1
On Thu, Oct 24, 2013 at 3:01 AM, Sylvain Lebresne wrote:
> Tracing has been fixed and a few bonus bug have been fixed since the first
> strike, let try again: I propose the following artifacts for release as
> 2.0.2.
>
> sha1: 22e67be8fec2132c6480a63d3b99946a4fabb3a5
> Git:
>
> http://git-wip
+1
On Wed, Nov 20, 2013 at 3:37 AM, Sylvain Lebresne wrote:
> A fair number of fixes went in since 1.2.11, I propose the following
> artifacts
> for release as 1.2.12.
>
> sha1: 026865f2a36d9685057c407e3fa528c101ab46b7
> Git:
>
> http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;
+1
On Thu, Nov 21, 2013 at 5:20 AM, Sylvain Lebresne wrote:
> Lots of changes since 2.0.2, I propose the following artifacts for release
> as
> 2.0.3.
>
> sha1: c11bbecec82f4b27d3d7560bb69fc0bdc8281b9d
> Git:
>
> http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/2.0.2
+1
On Fri, Nov 22, 2013 at 2:54 AM, Sylvain Lebresne wrote:
> With now CASSANDRA-6374 included, I propose the following artifacts for
> release as
> 2.0.3.
>
> sha1: 3c9760bdb986f6c2430adfc13c86ecb75c3246ac
> Git:
>
> http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/
+1
On Wed, Dec 11, 2013 at 9:24 AM, Sylvain Lebresne wrote:
> Bugs fixed, good. I propose the following artifacts for release as 1.2.13.
>
> sha1: 6ab82a46984ccbf5eed4244ceef6fa30d781eebb
> Git:
>
> http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/1.2.13-tentative
>
+1
On Mon, Dec 16, 2013 at 3:38 AM, Sylvain Lebresne wrote:
> So now that CASSANDRA-6485 has been committed, I propose the following
> artifacts for release as 1.2.13.
>
> sha1: 4be9e6720d9f94a83aa42153c3e71ae1e557d2d9
> Git:
>
> http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;
Changing to -1 as
https://issues.apache.org/jira/browse/CASSANDRA-6488seems to be a real
problem.
On Mon, Dec 16, 2013 at 12:12 PM, Brandon Williams wrote:
> +1
>
>
> On Mon, Dec 16, 2013 at 3:38 AM, Sylvain Lebresne wrote:
>
>> So now that CASSANDRA-6485 has been com
Or rather: https://issues.apache.org/jira/browse/CASSANDRA-6493
I would still prefer a 24h vote after resolution though.
On Mon, Dec 16, 2013 at 5:56 PM, Brandon Williams wrote:
> Changing to -1 as https://issues.apache.org/jira/browse/CASSANDRA-6488seems
> to be a real problem.
>
&
You've been added (or will be once this page loads)
On Mon, Dec 16, 2013 at 6:46 PM, Dan Rollo wrote:
> Hi,
>
> The Cassandra Wiki says to request access on this list to edit the wiki. I
> found a minor typo, and would like to post a correction.
>
> Thanks,
> Dan
>
> (wiki id: bhamail)
>
>
>
+1
On Wed, Dec 18, 2013 at 3:46 AM, Sylvain Lebresne wrote:
> Third time's the charm, I propose the following artifacts for release as
> 1.2.13.
>
> sha1: 1b4c9b45cbf32a72318c42c1ec6154dc1371e8e2
> Git:
>
> http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/1.2.13-tent
--- Original Message --
> From: "Michael Kjellman"
> To: "dev@cassandra.apache.org" ; "Roman
> Vasilyev"
> Cc: "Brandon Williams"
> Sent: 12/19/2013 11:38:54 AM
> Subject: Re: Re[2]: C* engine
>
> You seem to think something like t
I can agree with you on Java, but the JVM is a different matter. It is
wonderful.
On Thu, Dec 19, 2013 at 1:50 PM, Oscar Bonilla <6f6...@gmail.com> wrote:
> Roman,
>
> I would start with figuring out exactly how much performance you’re losing
> because of the language and whether there is lower
That's why we move things off-heap.
On Thu, Dec 19, 2013 at 1:57 PM, Roman Vasilyev wrote:
> One of the core problems what I can see is garbage collection, it blocks
> whole server just to clean memory, same stuff with periods of it. On high
> load you constantly have to control does the heap cl
Let's ask what we'll lose here.
4 years of work, tons of debugging, loads of instrumentation, for what
gain? Almost nil.
On Thu, Dec 19, 2013 at 1:22 PM, Roman Vasilyev wrote:
> Hello,
>
> Don't want to rise "holy war". Just let me share my crazy thoughts.
> I believe it could improve Cassandr
+1
On Fri, Dec 27, 2013 at 1:25 PM, Eric Evans wrote:
>
>
> #6527[1] could cause data loss, so I propose the following artifacts for
> release as 2.0.4
>
> Git: 2.0.4-tentative/d56f8f2
> Gitweb:
> https://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=commit;h=d56f8f2
> Artifacts:
> https://
+1
On Fri, Jan 31, 2014 at 5:33 AM, Sylvain Lebresne wrote:
> I propose the following artifacts for release as 1.2.14.
>
> sha1: 6a9314408cbd69ce26c2ba04bf49df7809a911bf
> Git:
>
> http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/1.2.14-tentative
> Artifacts:
>
> htt
+1
On Fri, Jan 31, 2014 at 1:33 PM, Sylvain Lebresne wrote:
> sha1: 0191b359fc18ebb1efa940257729d141c26112d3
> Git:
>
> http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/2.0.5-tentative
> Artifacts:
>
> https://repository.apache.org/content/repositories/orgapachecassa
+1
On Feb 3, 2014 3:08 AM, "Sylvain Lebresne" wrote:
> With typo introduced by CASSANDRA-6505 fixed, I propose the following
> artifacts
> for release as 2.0.5.
>
> sha1: b71372146135fdcee6353ec8254ebfd87c42f907
> Git:
>
> http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/t
+1
On Feb 5, 2014 2:24 AM, "Sylvain Lebresne" wrote:
> We just released 1.2.14 but unfortunately it shipped with a relatively
> serious
> regression: https://issues.apache.org/jira/browse/CASSANDRA-6648. That
> regression has been fixed, but we need to get that fix to users, so I
> propose
> the
+1
On Feb 5, 2014 3:50 AM, "Sylvain Lebresne" wrote:
> As said while closing the previous vote, we needed to re-roll for
> CASSANDRA-6648, so I propose the following artifacts for release as 2.0.5.
> I also propose an expedited 24h vote.
>
> sha1: 29670eb6692f239a3e9b0db05f2d5a1b5d4eb8b0
> Git:
>
+1
On Mon, Feb 17, 2014 at 11:23 AM, Sylvain Lebresne wrote:
> Cassandra 2.1 is coming along but we now need wider testing. So I propose
> the
> following artifacts for release as 2.1.0-beta1. Let it be clear that it is
> only
> a beta (and the first one at that), so we know it's not perfect, bu
A few:
https://issues.apache.org/jira/browse/CASSANDRA-4914
https://issues.apache.org/jira/browse/CASSANDRA-5184
https://issues.apache.org/jira/browse/CASSANDRA-6704
https://issues.apache.org/jira/browse/CASSANDRA-6167
On Thu, Feb 27, 2014 at 7:50 AM, David Semeria wrote:
> Hi List,
>
> I w
+1
On Fri, Mar 7, 2014 at 9:52 AM, Sylvain Lebresne wrote:
> We're starting to have a really big changelog so I propose the following
> artifacts for release as 2.0.6.
>
> sha1: 656edc529db59f0002a7fb0eed93339071fd3974
> Git:
>
> http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;
As someone who has written a thrift wrapper, +1
On Tue, Mar 11, 2014 at 12:00 PM, Jonathan Ellis wrote:
> CQL3 is almost two years old now and has proved to be the better API
> that Cassandra needed. CQL drivers have caught up with and passed the
> Thrift ones in terms of features, performance
How about the myriad of thrift wrappers that aren't in-tree either?
On Tue, Mar 11, 2014 at 3:03 PM, Edward Capriolo wrote:
> "Other databases treat this issue differently, and there are a set of
> tradeoffs. Mysql's decision may not be the best for Cassandra."
>
> Do you know of any other data
eats non java
> people like second class citizens"
>
>
> http://mail-archives.apache.org/mod_mbox/hbase-user/201108.mbox/%3ccafk14gsrnysj_oev2_utwc-+u4ssdmdsmp2dgrst90hoypw...@mail.gmail.com%3E
>
> Nice to see us pulling a total 180.
>
>
> On Tue, Mar 11, 2014 at
On Tue, Mar 11, 2014 at 6:53 PM, Joe Stein wrote:
> Is there a wiki page for the protocol spec? I googled a little but my
> google fu is off today :(
>
>
We keep that in-tree:
https://github.com/apache/cassandra/blob/trunk/doc/native_protocol_v2.spec
+1
On Mon, Mar 24, 2014 at 12:24 PM, Sylvain Lebresne wrote:
> I propose the following artifacts for release as 1.2.16.
>
> sha1: 05fcfa2be4eba2cd6daeee62d943f48c45f42668
> Git:
>
> http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/1.2.16-tentative
> Artifacts:
>
> ht
+1
On Thu, Mar 27, 2014 at 9:44 AM, Sylvain Lebresne wrote:
> So, seems like CASSANDRA-6924 was kind of a false alarm. And since I've
> never dropped
> the artifacts and no commit has been done on 1.2 since then, I propose to
> just resurrect the
> vote. Since the vote had initially ran for 2 da
+1
On Apr 14, 2014 10:39 AM, "Sylvain Lebresne" wrote:
> sha1: 7dbbe9233ce83c2a473ba2510c827a661de99400
> Git:
>
> http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/2.0.7-tentative
> Artifacts:
>
> https://repository.apache.org/content/repositories/orgapachecassandra-1
+1
On Thu, May 1, 2014 at 11:01 AM, Sylvain Lebresne wrote:
> It's time to get the 2nd beta for 2.1 out. Note that we know it's not bug
> free
> at all, but every main features we wanted for 2.1 is in, so we want to get
> that
> out to get as much testing as possible to get a solid RC1.
>
> sha1
With the lack of votes, the other issues mentioned in this thread, and most
importantly the reopening of CASSANDRA-6285 (which should be trivial to
solve), I'll throw down the -1.
On Tue, May 6, 2014 at 4:12 AM, Sylvain Lebresne wrote:
> Since a fair amount of bug fixes have been committed since
401 - 500 of 933 matches
Mail list logo
