With 6 binding +1, 3 non-binding +1 and no -1 the vote passes
On Fri, Jul 1, 2016 at 3:49 PM, Dave Brosius
wrote:
> +1
>
> On 06/30/2016 03:30 PM, Jake Luciani wrote:
>
>> I propose the following artifacts for release as 2.1.15.
>>
>> sha1: cb14186f8d6c2d110
>
> With 6 binding +1, 3 non-binding +1 and no -1 the vote passes
>
> On Sat, Jul 2, 2016 at 3:46 AM, Tommy Stendahl <
> tommy.stend...@ericsson.com> wrote:
>
>> +1 (non-binding)
>>
>>
>> On 2016-07-01 16:58, Jake Luciani wrote:
>>
>
With 5 binding +1, 2 non-binding +1 and no -1 the vote passes
On Tue, Jul 5, 2016 at 6:44 AM, Aleksey Yeschenko
wrote:
> +1
>
> --
> AY
>
> On 1 July 2016 at 16:41:00, Jake Luciani (j...@apache.org) wrote:
>
> I propose the following artifacts for re
The Cassandra team is pleased to announce the release of Apache Cassandra
version 2.1.15.
Apache Cassandra is a fully distributed database. It is the right choice
when you need scalability and high availability without compromising
performance.
http://cassandra.apache.org/
Downloads of source a
The Cassandra team is pleased to announce the release of Apache Cassandra
version 3.0.8.
Apache Cassandra is a fully distributed database. It is the right choice
when you need scalability and high availability without compromising
performance.
http://cassandra.apache.org/
Downloads of source an
The Cassandra team is pleased to announce the release of Apache Cassandra
version 2.2.7.
Apache Cassandra is a fully distributed database. It is the right choice
when you need scalability and high availability without compromising
performance.
http://cassandra.apache.org/
Downloads of source an
Also, anything related to native protocol v5
https://issues.apache.org/jira/issues/?jql=labels%20%3D%20protocolv5
On Wed, Jul 20, 2016 at 11:30 AM, Jason Brown wrote:
> forgot to mention that 8457 changes the internode messaging protocol, so
> needs to fall on a major version boundary.
>
> If 84
+1
On Wed, Jul 20, 2016 at 6:04 PM, Brandon Williams wrote:
> +1
>
> On Wed, Jul 20, 2016 at 4:48 PM, Michael Shuler
> wrote:
>
> > I propose the following artifacts for release as 3.8.
> >
> > sha1: c3ded0551f538f7845602b27d53240cd8129265c
> > Git:
> >
> >
> http://git-wip-us.apache.org/repos/
Will that be in 3.x or 4?
On Wed, Jul 20, 2016 at 8:20 PM, Aleksey Yeschenko
wrote:
> I don’t think so, b/c
> https://issues.apache.org/jira/browse/CASSANDRA-12142 will allow us to
> develop them incrementally.
>
> --
> AY
>
> On 20 July 2016 at 22:03:37, Jake Luciani
-1
On Thu, Jul 28, 2016 at 2:19 PM, Aleksey Yeschenko
wrote:
> Let me sum up my thoughts so far.
>
> Some of the most important goals of tick-tock were 1) predictable, regular
> releases with manageable changesets and
> 2)individual releases that are more stable than in our previous process.
>
>
r.
>
> As fun as it is to type -1.
>
>
> On Thursday, 28 July 2016, Jake Luciani > wrote:
>
> > -1
> >
> > On Thu, Jul 28, 2016 at 2:19 PM, Aleksey Yeschenko
> > wrote:
> >
> > > Let me sum up my thoughts so far.
> > >
> &
I think I outlined the tradeoffs I see between the roll our own vs use a
reactive framework in
https://issues.apache.org/jira/plugins/servlet/mobile#issue/CASSANDRA-10528
My view is we should try to utilize the existing before we start writing
our own. And even if we do write our own keep it react
Jake could you show an example issue and how the pipeline works?
On Fri, Aug 26, 2016 at 12:03 PM, Jake Farrell wrote:
> We just switched Apache Thrift over to using Github for all our inbound
> contributions, have not made Github canonical yet. We wanted to have one
> unified way to accept patc
+1 so long as it filters out the join/leave stuff :)
On Fri, Aug 26, 2016 at 1:42 PM, Jeff Jirsa
wrote:
> There exists a #cassandra-dev IRC channel that’s historically been used by
> developers discussing the project – while it’s public, it’s not archived,
> and it’s not a mailing list. The ASF
I'm pretty sure everyone will agree Tick-Tock didn't go well and needs to
change.
The problem for me is going back to the old way doesn't sound great. There
are parts of tick-tock I really like,
for example, the cadence and limited scope per release.
I know at the summit there were a lot of ideas
I propose the following artifacts for release as 3.0.9.
sha1: d600f51ee1a3eb7b30ce3c409129567b70c22012
Git:
http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/3.0.9-tentative
Artifacts:
https://repository.apache.org/content/repositories/orgapachecassandra-1124/org/apache
With 11 binding +1, 5 non-binding +1 and no -1 the vote passes. I will
publish.
On Mon, Sep 19, 2016 at 2:19 AM, Tommy Stendahl wrote:
> +1 (non binding)
>
>
>
> On 2016-09-15 20:57, Jake Luciani wrote:
>
>> I propose the following artifacts for rele
The Cassandra team is pleased to announce the release of Apache Cassandra
version 3.0.9.
Apache Cassandra is a fully distributed database. It is the right choice
when you need scalability and high availability without compromising
performance.
http://cassandra.apache.org/
Downloads of source an
No I'm not using a seq anywhere else then the command line
On Oct 13, 2016 4:40 PM, "Ben Slater (JIRA)" wrote:
>
> [ https://issues.apache.org/jira/browse/CASSANDRA-12490?
> page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&
> focusedCommentId=15573119#comment-15573119 ]
The main point is to avoid keeping things in the page cache that are no
longer needed like compacted data that has been early opened elsewhere.
On Oct 18, 2016 11:29 AM, "Michael Kjellman"
wrote:
> We use posix_fadvise in a bunch of places, and in stereotypical Cassandra
> fashion no comments we
if it turned out
> not to be wouldn't it be better in this case to have kernel be smart at
> what it's best at?
>
> best,
> kjellman
>
> On Oct 18, 2016, at 8:50 AM, Jake Luciani mailto:jaker
> s...@gmail.com>> wrote:
>
> The main point is to avoid keepi
Hi Tyler,
There is a nice guide now in the docs on how to contribute[1].
If you try it and find holes you can also help by contributing to those
docs.
-Jake
[1]: http://cassandra.apache.org/doc/latest/development/index.html
On Sat, Nov 5, 2016 at 11:08 AM, Tyler Tolley
wrote:
> Just want to we
-1 due to https://issues.apache.org/jira/browse/CASSANDRA-11039
It's a small fix but a critical bug. I'll patch shortly
On Nov 11, 2016 2:32 AM, "Tommy Stendahl"
wrote:
> +1 (non-binding)
>
>
> On 2016-11-08 21:08, Michael Shuler wrote:
>
>> I propose the following artifacts for release as 3.0.
Should I merge the fix to just the 3.0.10 tag? or should we include the 3
new tickets that went into 3.0.11 already? I see no issue with the latter
since they are bugfixes
On Fri, Nov 11, 2016 at 8:48 AM, Jake Luciani wrote:
> -1 due to https://issues.apache.org/jira/browse/CASSANDRA-11
+1
On Nov 11, 2016 9:18 PM, "Jeff Jirsa" wrote:
> +1
>
> --
> Jeff Jirsa
>
>
> > On Nov 11, 2016, at 5:36 PM, Michael Shuler
> wrote:
> >
> > I propose the following artifacts for release as 3.0.10.
> >
> > sha1: d6a3ef4863142c3f9fc1def911f28341fc78f2e8
> > Git:
> > http://git-wip-us.apache.org
I think the main blocker is identifying and contacting the folks who have
contributed code to dtest without an ICLA
On Mon, Nov 21, 2016 at 4:40 AM, Dave Lester wrote:
> I may have missed further email discussion or updates, but since the
> October 3rd email accepting dtest to the project has th
Another option would be to add a unsubscribe header, not sure if we already
do but I think that causes gmail/outlook to add a unsubscribe button
http://www.list-unsubscribe.com/
On Wed, Apr 26, 2017 at 11:24 AM, Eric Evans
wrote:
> On Wed, Apr 26, 2017 at 9:36 AM, Jake Farrell wrote:
> > moder
>
> The remaining issues are:
>
> * There's no way to determine if a view is out of sync with the base table.
> * If you do determine that a view is out of sync, the only way to fix it
> is to drop and rebuild the view.
> * There are liveness issues with updates being reflected in the view.
>
I ju
guarantees than many users might be able to readily achieve, and they
> don't know this. Even for those users we can offer better guarantees, it
> is in my opinion fundamentally a problem to offer a tool we do not fully
> understand or fully explain/caveat the behaviour of.
>
>
>
I never used the word easier. I think it's a hard problem but it should be
our problem if we want people to use our database.
I have little opinion of if MVs should be made experimental or opt-in. I'd
simply discussing the need for this feature (as opposed to ripping it out)
Yeah I worked around this by skipping all but the last call. I need to fix this
properly. Thx for the reminder :)
On Jul 19, 2012, at 7:47 PM, Jonathan Ellis wrote:
> That smells like a bug to me. I don't see how you can avoid getting
> multiple buildIndexAsync calls kicked off.
>
> What d
+1
On Fri, Jul 27, 2012 at 12:38 PM, Sylvain Lebresne 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:
> http://git-wip-us.apache.o
+1
On Oct 9, 2012, at 11:48 AM, Sylvain Lebresne wrote:
> Quite a few fixes since 1.1.5 and there's at least #4772 that makes it worth
> pushing a new release. So I propose the following artifacts for release as
> 1.1.6.
>
> sha1: 2773f7cd8ba5e9b3b293f26f546ddcd450831d82
> Git:
> http://git
+1
On Oct 13, 2012, at 4:13 PM, Brandon Williams wrote:
> +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: a
+1
On Dec 3, 2012, at 1: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 Dec 29, 2012 7: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.apache.org/repos/asf?p
+1
On Wed, Feb 6, 2013 at 5:32 PM, Gary Dusbabek wrote:
> +1
>
>
> 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, ex
+1
On Mon, Apr 8, 2013 at 3:41 PM, Carl Yeksigian <
cyeksig...@bluemountaincapital.com> wrote:
> +1
>
> On Apr 8, 2013, at 1:55 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: 2e96d07
There is a issue with
https://issues.apache.org/jira/browse/CASSANDRA-4860
There is a workaround but it should probably be fixed before 1.2.5 comes
out.
On Tue, May 7, 2013 at 9:27 AM, Jonathan Ellis wrote:
> +1
>
> On Mon, May 6, 2013 at 3:15 AM, Sylvain Lebresne
> wrote:
> > Now that the o
+1
On Wed, May 15, 2013 at 10: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=c
+1
On Tue, Aug 27, 2013 at 9:33 AM, Michael Kjellman
wrote:
> +1
>
> This is currently broken.
>
> > On Aug 27, 2013, at 5:14 AM, "Chris Burroughs" <
> chris.burrou...@gmail.com> wrote:
> >
> > Following up on a discussion in IRC. A caveat on the (not new, but not
> > fixed) problems with repla
+1
On Wed, Aug 28, 2013 at 10: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:
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 wrote:
>
>> It's all yours.
>>
>> On Thu, Sep 19, 2013 at 12:27 PM, Jason Brown
>
I've been working on 5417
On Thu, Sep 19, 2013 at 1:33 PM, Jonathan Ellis wrote:
> It's all yours.
>
> On Thu, Sep 19, 2013 at 12:27 PM, Jason Brown
> wrote:
> > Seeing Sylvain's comment to hold off on 4175, do you mind if I take a
> whack
> > at 6060?
> > On Sep 19, 2013 9:35 AM, "Jonathan El
+1
On Thu, Sep 19, 2013 at 6: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 Thu, May 1, 2014 at 12:01 PM, 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
I think having cql unit tests is certainly a good idea. It doesn't replace
dtests but makes it easier to have better coverage locally.
On Tue, May 20, 2014 at 7:10 PM, Tyler Hobbs wrote:
> Sylvain and I have been having a discussion about testing CQL in unit tests
> vs dtests. I'd like to hea
Jython! :D
On Thu, May 22, 2014 at 12:09 PM, Benedict Elliott Smith <
belliottsm...@datastax.com> wrote:
> I would for defining the cql tests in a way that permits them being run as
> both dtests and unit tests. But since we're on python for dtests that could
> be troublesome.
>
>
> On 22 May 20
Very Late +1
On Fri, May 30, 2014 at 12:38 PM, Sylvain Lebresne
wrote:
> We've fixed all the bugs we had open for 2.1 so it's time to move on
> towards
> the final release. I thus propose the following artifacts for release as
> 2.1.0-rc1.
>
> sha1: c108ce5bf2abc88077c97924def59fa1ea98a66e
> Gi
Hi Michael,
I didn't get to hear the in person conversation so taking a step back.
The proposal seems to be in response to a common problem. i.e. I'm on C*
version X and I need feature Y which is only available on version Z. Is
this correct?
The options have been: a) upgrade to version Z or b)
write it against the months worth of changes that have
> happened since.
>
> Finally, it's an attempt to make the internal forking not as common as it
> might be today. As you said - this is somewhat of a common process.
>
> > On Jun 17, 2014, at 8:52 AM, "Jake Lucian
;
> > And then the experimentals into each other:
> >
> > 1.2ex->2.0ex, 2.0ex->2.1ex, 2.1ex->3.0ex
> >
> > That's quite a lot of merging in the end.
> >
> >
> > On Tue, Jun 17, 2014 at 11:51 AM, Jake Luciani wrote:
> >
> >&g
+1
On Mon, Jun 23, 2014 at 1:59 PM, Sylvain Lebresne
wrote:
> We've almost there. I propose the following artifacts for release as
> 2.1.0-rc2.
>
> sha1: e2bef02e254a9c6e37a86cab957a1fcba56214fd
> Git:
>
> http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/2.1.0-rc2-t
+1
On Wednesday, July 2, 2014, Jason Brown wrote:
> +1
>
>
> On Wed, Jul 2, 2014 at 5:56 AM, Jonathan Ellis > wrote:
>
> > +1
> > On Jul 2, 2014 4:36 AM, "Sylvain Lebresne" > wrote:
> >
> > > 1.2.17 shipped with a reference to a java 7 class (see CASSANDRA-7147).
> > As
> > > consequence, the
+1
On Tue, Jul 8, 2014 at 9:24 AM, Sylvain Lebresne
wrote:
> Getting closer. I propose the following artifacts for release as 2.1.0-rc3.
> Also, unless
> someone has an objection, I'm also proposing to exceptionally do a shorter
> 48h
> vote period, mainly because it's easier for me this time (
+1
On Saturday, August 2, 2014, Sylvain Lebresne wrote:
> I propose the following artifacts for release as 2.1.0-rc5. Unless someone
> strongly
> object, we'll keep the vote period for this one to 24h.
>
> sha1: cfb335e39b080c031faf76671c67cc003af22635
> Git:
>
> http://git-wip-us.apache.org/rep
+1
On Saturday, August 9, 2014, Sylvain Lebresne wrote:
> I propose the following artifacts for release as 2.1.0-rc6. Unless someone
> strongly
> object, we'll keep the vote period for this one to 24h.
>
> sha1: cfb335e39b080c031faf76671c67cc003af22635
> Git:
>
> http://git-wip-us.apache.org/rep
+1
On Sunday, August 17, 2014, Sylvain Lebresne wrote:
> Let's try again. I propose the following artifacts for release as
> 2.1.0-rc6.
> The vote will be open 24h.
>
> sha1: d087317fdd0a2b35c0ee7473d6c83f0b24ced27d
> Git:
>
> http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=r
The file should be in the build/lib/jars
directory compile-command-annotations-1.2.0.jar
Do you see that in the .classpath file?
On Sun, Aug 24, 2014 at 11:51 PM, wateray wrote:
> Hi all，
>
>
>
> I just learn Cassandra for a few days. When I want to debug Cassandra
> with eclipse.
>
> I fol
+1
On Tue, Sep 2, 2014 at 8:13 AM, Sylvain Lebresne
wrote:
> We've fixed CASSANDRA-7239 and added CASSANDRA-7857, times to try this
> again: I
> propose the following artifacts for release as 2.1.0-rc7. And since it's
> not
> yet the final, let's stick to a short 24h vote.
>
> sha1: 02be0dedd97
+1
On Sun, Sep 7, 2014 at 10:23 AM, Sylvain Lebresne
wrote:
> We have no outstanding tickets open and tests are in the green, so I
> propose
> the following artifacts for release as 2.1.0.
>
> sha1: c6a2c65a75adea9a62896269da98dd036c8e57f3
> Git:
>
> http://git-wip-us.apache.org/repos/asf?p=cas
I propose the following artifacts for release as 1.2.19. This will likely
be the last release in this series.
sha1: 2d29ebd41592d83f899cbbf56823f1f5bf0f01c9
Git:
http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/1.2.19-tentative
Artifacts:
https://repository.apache.org
With 5 binding, 2 non-binding +1 and no -1 the vote passes. I'll publish
the release
On Fri, Sep 12, 2014 at 1:16 PM, Jake Luciani wrote:
> I propose the following artifacts for release as 1.2.19. This will likely
> be the last release in this serie
-1 Just realized I only committed
https://issues.apache.org/jira/browse/CASSANDRA-8027 to 2.1 and not 2.0 as
well. Will post a fix for 2.0 shortly
On Fri, Oct 17, 2014 at 8:36 AM, Jonathan Ellis wrote:
> +1
>
> On Fri, Oct 17, 2014 at 6:48 AM, Sylvain Lebresne
> wrote:
>
> > I propose the fol
+1
On Tue, Oct 21, 2014 at 11:37 AM, Sylvain Lebresne
wrote:
> I propose the following artifacts for release as 2.0.11.
>
> sha1: 02b83d9a8c240ad94461fb305cc90f275fba03b3
> Git:
>
> http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/2.0.11-tentative
> Artifacts:
>
> ht
+1
On Tuesday, October 21, 2014, Sylvain Lebresne wrote:
> I propose the following artifacts for release as 2.1.1.
>
> sha1: 3261d5e668f341464fc322b6bc424b33ce3adffd
> Git:
>
> http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/2.1.1-tentative
> Artifacts:
>
> https://
Hello,
There is currently an issue with the apache debian repo for cassandra.
ASF infrastructure is working on fixing this
https://issues.apache.org/jira/browse/INFRA-8558
Sorry for the inconvenience.
-Jake
I propose the following artifacts for release as 2.1.2.
sha1: cdf80d9d196171376b6fc7aface473a471313efb
Git:
http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/2.1.2-tentative
Artifacts:
https://repository.apache.org/content/repositories/orgapachecassandra-1039/org/apache
With 5 binding +1, 3 non-binding +1 and no -1 the vote passes. I'll
release the artifacts
The Cassandra team is pleased to announce the release of Apache Cassandra
version 2.1.2.
Apache Cassandra is a fully distributed database. It is the right choice
when you need scalability and high availability without compromising
performance.
http://cassandra.apache.org/
Downloads of source an
Hi Andrew,
I'm happy to help.
-Jake
On Tue, Jan 6, 2015 at 2:19 PM, Andrew Bayer wrote:
> Hi Cassandra team -
>
> So as you're probably aware, the Cassandra Debian packages currently on
> dist need to be moved off there. The Infra team has been working on a
> solution for that - we've got an o
you give us a sense of what your needs for the
> repo are? What are you putting in it? Are you splitting it up by distro at
> all or just putting new versions of Cassandra in each time?
>
> A.
>
> On Wed, Jan 7, 2015 at 7:15 AM, Jake Luciani wrote:
>
>> Hi Andrew,
>>
an
> use a generic repo that allows you to just upload files/directories, so you
> could keep doing what you're doing now but upload to Bintray rather than
> dist.
>
> Others on the Infra team will know for sure, but I'm pretty confident that a
> redirect from dist to bin
I propose the following artifacts for release as 2.0.12.
sha1: df1f5ead0950d4d3058cf6fe0fcae9ef528014fa
Git:
http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/2.0.12-tentative
Artifacts:
https://repository.apache.org/content/repositories/orgapachecassandra-1041/org/ap
gt; On Sat, Jan 10, 2015 at 9:25 AM, Sylvain Lebresne
> wrote:
>>
>> +1
>>
>> On Sat, Jan 10, 2015 at 1:32 AM, Aleksey Yeschenko
>> wrote:
>>
>> > +1
>> >
>> > --
>> > AY
>> >
>> > On January 10, 2015 at 1:35
I propose the following artifacts for release as 2.0.12.
sha1: 90780b550f39bc318567ac53f8e8e7d797697f16
Git:
http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/2.0.12-tentative
Artifacts:
https://repository.apache.org/content/repositories/orgapachecassandra-1042/org/ap
Any update?
On Fri, Jan 9, 2015 at 12:53 PM, Andrew Bayer wrote:
> I'm investigating this now - will update when I have more information.
>
> A.
>
> On Fri, Jan 9, 2015 at 7:54 AM, Jake Luciani wrote:
>
>> The docs seems to indicate signing happens at the orga
o sign organization Debian repository metadata. I'll
>> ping them for an update.
>>
>> A.
>>
>>
>> On Thursday, January 15, 2015, Jake Luciani wrote:
>>>
>>> Any update?
>>>
>>> On Fri, Jan 9, 2015 at 12:53 PM, Andrew Ba
Let's try again. I propose the following artifacts for release as 2.0.12.
sha1: ce207cba413381986324f2c8edad9e090e5be5b1
Git:
http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/2.0.12-tentative
Artifacts:
https://repository.apache.org/content/repositories/orgapachecass
That's 5 binding +1 including mine. No -1 votes. Vote passes I'll
finish the release
On Mon, Jan 19, 2015 at 3:05 AM, Sylvain Lebresne wrote:
> +1
>
> On Sat, Jan 17, 2015 at 10:04 PM, Gary Dusbabek wrote:
>
>> +1
>> On Jan 16, 2015 9:41 PM, "Jake Luci
The Cassandra team is pleased to announce the release of Apache Cassandra
version 2.0.12.
Apache Cassandra is a fully distributed database. It is the right choice
when you need scalability and high availability without compromising
performance.
http://cassandra.apache.org/
Downloads of source a
I propose the following artifacts for release as 2.1.3.
sha1: c1a2e0fa585877c057b7a8958adeacf6a589c126
Git:
http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/2.1.3-tentative
Artifacts:
https://repository.apache.org/content/repositories/orgapachecassandra-1044/org/apac
ovnode_dtest/470/testReport/
> to:
> http://cassci.datastax.com/job/cassandra-2.1_novnode_dtest/472/testReport/
>
> --
> Michael
>
>
> On 02/09/2015 10:50 AM, Jake Luciani wrote:
>>
>> I propose the following artifacts for release as 2.1.3.
>>
>> sha1:
I propose the following artifacts for release as 2.1.3.
sha1: 7cc1cf000c6b48bc13aa551467f27e4ab28b2031
Git:
http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/2.1.3-tentative
Artifacts:
https://repository.apache.org/content/repositories/orgapachecassandra-1046/org/apac
, Gary
Dusbabek
+1
On Wed, Feb 11, 2015 at 5:59 PM, Gary Dusbabek wrote:
> +1
>
> On Wed, Feb 11, 2015 at 8:35 AM, Jake Luciani wrote:
>
> > I propose the following artifacts for release as 2.1.3.
> >
> > sha1: 7cc1cf000c6b48bc13aa551467f27e4ab28b2031
> >
The Cassandra team is pleased to announce the release of Apache Cassandra
version 2.1.3.
This release contains over 100 fixes for 2.1 so anyone on 2.1.X should
upgrade to this ASAP.
Apache Cassandra is a fully distributed database. It is the right choice
when you need scalability and high availa
That would be great! By all means, it's open to work on. Please
comment on the ticket if you get stuck, have questions etc.
On Wed, Feb 18, 2015 at 12:13 PM, Jatin Ganhotra
wrote:
> Hi,
>
> We are a team of 3 graduate students in Computer Science at University of
> Illinois at Urbana Champaign.
>
I propose the following artifacts for release as 2.0.13.
sha1: 20593c24a9f8c07aff8f848f4b5774ed88ea4687
Git:
http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/2.0.13-tentative
Artifacts:
https://repository.apache.org/content/repositories/orgapachecassandra-1047/org/ap
On Thu, Mar 12, 2015 at 8:55 PM, Jake Luciani wrote:
> I propose the following artifacts for release as 2.0.13.
>
> sha1: 20593c24a9f8c07aff8f848f4b5774ed88ea4687
> Git:
> http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/2.0.13-tentative
> Artifacts
Apache Cassandra is a fully distributed database. It is the right choice
when you need scalability and high availability without compromising
performance.
http://cassandra.apache.org/
Downloads of source and binary distributions are listed in our download
section:
http://cassandra.apache.org/d
+1
On Tue, Mar 17, 2015 at 5:06 PM, Jonathan Ellis wrote:
> Cassandra 2.1 was released in September, which means that if we were on
> track with our stated goal of six month releases, 3.0 would be done about
> now. Instead, we haven't even delivered a beta. The immediate cause this
> time is bl
CVE-2015-0225: Apache Cassandra remote execution of arbitrary code
Severity: Important
Vendor:
The Apache Software Foundation
Versions Affected:
Cassandra 1.2.0 to 1.2.19
Cassandra 2.0.0 to 2.0.13
Cassandra 2.1.0 to 2.1.3
Description:
Under its default configuration, Cassandra binds an unauthen
+1
On Sat, Apr 24, 2021 at 7:29 PM Sylwester Lachiewicz
wrote:
> +1 nb
> Sylwester
>
> On 2021/04/23 09:35:29 Aleksey Yeshchenko wrote:
> > +1
> >
> > > On 23 Apr 2021, at 08:51, Sam Tunnicliffe wrote:
> > >
> > > +1
> > >
> > >> On 23 Apr 2021, at 04:19, Jasonstack Zhao Yang <
> jasonstack.z..
+1
On Tuesday, July 13, 2021, Ben Bromhead wrote:
> +1 (nb)
>
> On Wed, Jul 14, 2021 at 12:26 PM Andrés de la Peña <
> a.penya.gar...@gmail.com>
> wrote:
>
> > +1
> >
> > On Wed, 14 Jul 2021 at 00:39, Patrick McFadin
> wrote:
> >
> > > +1 (nb)
> > >
> > > On Tue, Jul 13, 2021 at 3:45 PM Brandon
+1
On Fri, Jul 23, 2021 at 11:31 AM Blake Eggleston
wrote:
> +1
>
> > On Jul 23, 2021, at 6:39 AM, Branimir Lambov <
> branimir.lam...@datastax.com> wrote:
> >
> > +1
> >
> >> On Fri, Jul 23, 2021 at 4:15 PM Aleksey Yeschenko
> >> wrote:
> >>
> >> +1
> >>
> On 23 Jul 2021, at 14:03, Joshu
Hi Benedict!
I haven't gone too deeply into this proposal but it's very exciting to see
this kind of innovation!
Some basic questions which are tangentially related with this effort I
didn't see covered in the CEP.
1. Will this effort eventually replace consistency levels in C*? I ask
because
Great thanks for the information
On Tue, Sep 7, 2021 at 12:44 PM Blake Eggleston
wrote:
> Hi Jake,
>
> > 1. Will this effort eventually replace consistency levels in C*? I ask
> > because one of the shortcomings of our paxos today is
> > it can be easily mixed with non serialized consistencies
+1
On Fri, Dec 9, 2022 at 12:21 PM Sam Tunnicliffe wrote:
> +1
>
> On 7 Dec 2022, at 21:40, Mick Semb Wever wrote:
>
>
> Proposing the (second) test build of Cassandra 4.1.0 for release.
>
> sha1: f9e033f519c14596da4dc954875756a69aea4e78
> Git:
> https://gitbox.apache.org/repos/asf?p=cassandra.
non binding +1
On Thu, Jan 6, 2011 at 1:13 PM, Sylvain Lebresne wrote:
> +1 (not binding)
>
> On Thu, Jan 6, 2011 at 7:07 PM, Brandon Williams wrote:
>
> > +1, for reals yo.
> >
> > On Thu, Jan 6, 2011 at 11:17 AM, Eric Evans
> wrote:
> >
> > >
> > > RC 4 seems to be holding up OK, shall we? I
Thanks Jonathan and Cassandra PMC!
Happy to help Cassandra take over the world!
-Jake
On Thu, Jan 13, 2011 at 1:41 PM, Jonathan Ellis wrote:
> The Cassandra PMC has voted to add Jake as a committer. (Jake is also
> a committer on Thrift.)
>
> Welcome, Jake, and thanks for the hard work!
>
> -
201 - 300 of 335 matches
Mail list logo
