+1
Regards,
On Fri, Nov 22, 2013 at 2:24 PM, 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
+1
Regards,
On Thu, Sep 19, 2013 at 3: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
Hi Jonathan,
I can try 5549, if you want.
Regards,
On Thu, Sep 19, 2013 at 10:50 AM, Jake Luciani wrote:
> Well 5417 and 5020 combined
>
>
> On Thu, Sep 19, 2013 at 1:50 PM, Jake Luciani wrote:
>
> > I've been working on 5417
> >
> >
> > On Thu, Sep 19, 2013 at 1:33 PM, Jonathan Ellis
> wro
+1
Regards,
On Mon, Jul 22, 2013 at 9:23 AM, Sylvain Lebresne wrote:
> A healthy amount of bugs have been found since beta1, so let's release a
> new
> beta to shake out the remaining ones before a RC. I thus propose the
> following
> artifacts for release as 2.0.0-beta2
>
> sha1: e0eacd28183b
+1
Regards,
On Tue, Jul 9, 2013 at 2: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 pe
+1
Regards,
On Sat, Jun 22, 2013 at 3: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
+1
Regards,
On Thu, Mar 14, 2013 at 3: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
+1
Regards,
On Thu, Feb 21, 2013 at 5:50 AM, Jason Brown wrote:
> +1
>
>
> On Thu, Feb 21, 2013 at 3:16 AM, Gary Dusbabek
> wrote:
>
> > +1
> >
> >
> > On Wed, Feb 20, 2013 at 6:01 PM, Sylvain Lebresne > >wrote:
> >
> > > We've fixed a fair amount of important fixes since 1.2.1 so I propose
+1
Regards,
On Wed, Feb 6, 2013 at 2: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
FYI,
Not sure about this particular problem,
https://github.com/Vijay2win/flume-cassandra-sink supports latest flume
version, if you want to try it out.
Regards,
On Sun, Jan 27, 2013 at 8:05 PM, Sri Ramya wrote:
> hi,
>
> I am storing flume events in to cassandra by using simpleCassandraSink
+1
Regards,
On Thu, Jan 24, 2013 at 11:53 PM, 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-
+1
Regards,
On Sat, Dec 29, 2012 at 4:40 AM, Sylvain Lebresne wrote:
> After a quiet 2nd release candidate, it is time to release the final 1.2.0.
> I thus propose the following artifacts for release as 1.2.0.
>
> sha1: 69337a43670f71ae1fc55e23d6a9031230423900
> Git:
>
> http://git-wip-us.apac
+1
Regards,
On Mon, Dec 3, 2012 at 10:43 AM, 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:
+1
Regards,
On Fri, Nov 30, 2012 at 12:12 PM, Jonathan Ellis wrote:
> The more I think about it, the more I think we should call 1.2-next,
> 2.0. I'd like to spend some time paying off our technical debt:
>
> - replace supercolumns with composites (CASSANDRA-3237)
> - rewrite counters (CASS
+1
Regards,
On Fri, Nov 30, 2012 at 2: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.
>
> sha1
+1
Regards,
On Fri, Sep 7, 2012 at 10:37 AM, 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: e395307893d93a01e976656f
+1
Regards,
On Fri, Jun 29, 2012 at 9:20 AM, Sylvain Lebresne 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:
> http://git-wip-us
+1
Regards,
On Fri, May 4, 2012 at 9:33 AM, Sylvain Lebresne 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:
> http://git-wip-us.apache.org/r
+1
Regards,
On Fri, Mar 23, 2012 at 3:26 AM, Sylvain Lebresne 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 candidate
>>> I envision vnodes as Cassandra master being a shared cache,memtables,
and manager for what we today consider a Cassandra instance.
It might be kind of problematic when you are moving the nodes you want the
data associated with the node to move too, otherwise it will be a pain to
cleanup after
On Mon, Mar 19, 2012 at 8:24 PM, Eric Evans wrote:
> I'm guessing you're referring to Rick's proposal about ranges per node?
>
May be, what i mean is little more simple than that... We can consider
every node having a multiple conservative ranges and moving those ranges
for bootstrap etc, instea
I also did create a ticket
https://issues.apache.org/jira/browse/CASSANDRA-3768 with some of the
reason why I would like to see vnodes in cassandra.
It can also potentially reduce the SSTable seeks which a node has to do to
query data in SizeTireCompaction if extended to the filesystem.
But 110% a
+1
Regards,
On Wed, Feb 22, 2012 at 6:57 AM, Sylvain Lebresne 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:
> http://git-wip-us.apache.org/repos/asf?p=cassa
+1
Regards,
On Mon, Dec 19, 2011 at 9:56 AM, Jonathan Ellis wrote:
> Just a reminder that for us to meet our four-month major release
> schedule (i.e., 1.1 = Feb 18), we need to code freeze on Jan 18, which
> is just about a month away on the calendar but significantly closer in
> terms of m
+1
Regards,
On Fri, Jan 13, 2012 at 1:44 AM, Sylvain Lebresne 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:
> http://gi
Thanks Jonathan and Cassandra PMC,
I am all set for 2.0 :)
Regards,
On Thu, Jan 12, 2012 at 10:06 PM, Jonathan Ellis wrote:
> The Apache Cassandra PMC has voted to add Vijay as a committer. Thank
> you Vijay, and we look forward to continuing to work with you!
>
> --
>
+1
Regards,
On Sat, Dec 10, 2011 at 6:10 PM, Sylvain Lebresne 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 since
+1
Regards,
On Sat, Dec 10, 2011 at 5:26 PM, Sylvain Lebresne 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 followin
+1
Regards,
On Wed, Oct 5, 2011 at 11:10 AM, Brandon Williams wrote:
> +1
>
> On Wed, Oct 5, 2011 at 9:28 AM, Jonathan Ellis wrote:
> > +1
> >
> > On Wed, Oct 5, 2011 at 8:20 AM, Sylvain Lebresne
> wrote:
> >> The 0.8.6 has had a good run, but enough fixes were made since then to
> >> warra
+1
Regards,
On Wed, Sep 14, 2011 at 8:56 AM, Sylvain Lebresne 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 som
+1
Regards,
On Wed, Sep 7, 2011 at 2:49 AM, Iroiso wrote:
> On 9/7/2011 10:28 AM, Eric Evans wrote:
>
>> On Mon, Sep 5, 2011 at 12:25 PM, Sylvain Lebresne
>> wrote:
>>
>>> Seems like enough awesomeness went in the 0.8 branch since 0.8.4 to
>>> warrant
>>> a new release. I thus propose the f
+1
Regards,
On Tue, Apr 19, 2011 at 6:35 PM, Eric Evans 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, cql-1.0.0.tar.gz,
> txcql-1.0.0.tar.gz and apache-cassandra-cql-1.0.0.jar. These ar
+1...
Regards,
On Tue, Jan 11, 2011 at 5:35 PM, Jonathan Ellis wrote:
> Way back in Nov 09, we did a users survey and asked what features
> people wanted to see. Here was my summary of the responses:
>
> http://www.mail-archive.com/cassandra-user@incubator.apache.org/msg01446.html
>
> Looki
+1
Regards,
On Tue, Aug 10, 2010 at 10:20 AM, Eric Evans wrote:
>
> Today is the Cassandra Summit in San Francisco, the first ever. As I
> type this, Jonathan Ellis is at the podium delivering the keynote, and
> the room is packed. It's truly amazing how far this project has come in
> such
+1
Regards,
On Sun, Jul 25, 2010 at 1:13 PM, Stu Hood wrote:
> The are a few tickets affecting the public API that Rackspace would really
> like to see make it into the 0.7-beta, since they will be very difficult to
> apply once a mass of people have gone through the readTablesFromYaml
> pro
+1
Regards,
On Tue, May 25, 2010 at 11:15 PM, Chris Goffinet wrote:
> +1
>
> -Chris
>
> On May 25, 2010, at 10:25 PM, Jonathan Ellis wrote:
>
> > +1
> >
> > On Mon, May 24, 2010 at 4:02 PM, Eric Evans
> wrote:
> >>
> >> As promised, here is the 0.6.2 vote.
> >>
> >> The list of changes from
+1
Regards,
On Wed, May 19, 2010 at 11:52 AM, Eric Evans wrote:
>
> At the time of this writing, there are 10 open bugs[1] that are marked
> for 0.6.2. Some of these are pretty trivial and/or have patches
> attached, others haven't seen any recent activity.
>
> [1]:
>
> https://issues.apache
h, Didnt realize that part
Regards,
On Sat, Apr 3, 2010 at 10:54 PM, Avinash Lakshman <
avinash.laksh...@gmail.com> wrote:
> I think that was on Apr 1st - perhaps a April Fools prank.
>
> Avinash
>
> On Sat, Apr 3, 2010 at 10:11 PM, Vijay wrote:
>
> &
FYI Wondering who this is, even though there is a lot more better reason
other than the ones listed in the email. :)
Regards,
-- Forwarded message --
From: Owen O'Malley
Date: Thu, Apr 1, 2010 at 8:19 AM
Subject: Re: [VOTE] Replace HBase with Cassandra
To: "gene...@hadoo
+1
Regards,
On Sun, Mar 28, 2010 at 2:49 PM, Chris Goffinet wrote:
> +1
>
> -Chris
>
> On Mar 28, 2010, at 9:02 AM, Eric Evans wrote:
>
> >
> > The 0.6.0 blockers are now out of the way and things are looking good. I
> > propose the following tag/artifacts for 0.6.0-rc1:
> >
> > SVN Tag:
> >
40 matches
Mail list logo
