+1
On Thu, Feb 6, 2025 at 8:37 AM J. D. Jordan wrote:
>
> +1 (nb)
>
> > On Feb 6, 2025, at 6:31 AM, Maxim Muzafarov wrote:
> >
> > +1 (nb)
> >
> >> On Thu, 6 Feb 2025 at 05:34, Patrick McFadin wrote:
> >>
> >> +1
> >>
> >>> On Wed, Feb 5, 2025 at 8:15 PM C. Scott Andreas
> >>> wrote:
> >>>
>
This is very cool!
I have done a POC that was similar but more akin to Aurora paper
whereby the commitlog itself would repair itself from peers
proactively using the seekable commitlog.
Can you explain the reason you prefer to reconcile on read? Having a
consistent commitlog would solve so many
Hi,
I originally worked on the management API sidecar mentioned above.
I'm excited to see there's renewed interest in the cql for ops concept.
Though it currently uses an agent to inject the local socket for cql
(so it can be used by older versions of Apache Cassandra),
Similar logic like the man
We (DataStax) have a FileSystemProvider for Astra we can provide.
Works with S3/GCS/Azure.
I'll ask someone on our end to make it accessible.
This would work by having a bucket prefix per node. But there are lots
of details needed to support things like out of bound compaction
(mentioned in CEP).
+1
On Tue, Jun 13, 2023 at 7:14 PM Nate McCall wrote:
> +1
>
> On Wed, Jun 14, 2023 at 2:15 AM Jeremy Hanna
> wrote:
>
>> Calling for a vote on CEP-8 [1].
>>
>> To clarify the intent, as Benjamin said in the discussion thread [2], the
>> goal of this vote is simply to ensure that the community
+1
On Thu, May 25, 2023 at 11:45 AM Jonathan Ellis wrote:
> Let's make this official.
>
> CEP:
> https://cwiki.apache.org/confluence/display/CASSANDRA/CEP-30%3A+Approximate+Nearest+Neighbor%28ANN%29+Vector+Search+via+Storage-Attached+Indexes
>
> POC that demonstrates all the big rocks, including
There has been progress on
https://issues.apache.org/jira/plugins/servlet/mobile#issue/CASSANDRA-8928
Which is similar to what datastax does for DSE. Would this be an acceptable
solution?
Jake
On Mon, Feb 20, 2023 at 11:17 AM guo Maxwell wrote:
> It seems “An alternative solution is to impleme
+1
On Mon, Dec 19, 2022 at 7:27 PM C. Scott Andreas
wrote:
> +1nb
>
> On Dec 19, 2022, at 1:27 PM, Josh McKenzie wrote:
>
>
> +1
>
> On Mon, Dec 19, 2022, at 11:54 AM, SAURABH VERMA wrote:
>
> +1
>
> On Mon, Dec 19, 2022 at 9:36 PM Benjamin Lerer wrote:
>
> +1
>
> Le lun. 19 déc. 2022 à 16:31,
+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.
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
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
+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
+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 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..
; >
> > If there is no consensus, a vote is held. Whether or not you
> consider the
> > vote from 2018 still valid, you still need to seek the consent of the
> > community for your action today. Or is that not sacrosanct anymore?
> >
> >
&g
t
> include branching, or not?
>
> If there is no consensus, a vote is held. Whether or not you consider the
> vote from 2018 still valid, you still need to seek the consent of the
> community for your action today. Or is that not sacrosanct anymore?
>
>
> On 24/09/2020, 16:22,
I'm sorry I see no issue with branching 4.0 as it was the thing we voted on
back in 2018. If you wish to extend the freeze you should call a new vote.
On Thu, Sep 24, 2020 at 11:15 AM Benedict Elliott Smith
wrote:
> Nobody has any problem with an external repository being maintained. Just
> be
> Today the community still has in force an explicit vote prohibiting thee
merge of this work. You must conduct a vote to rescind this decision.
Actually, the vote was defined to hold until beta release:
https://lists.apache.org/thread.html/5ee66f3986bf8308912c216bd1b5f9aea35443626db9f92cdca4d7
+1
On Mon, Jul 20, 2020 at 8:08 AM Andrés de la Peña
wrote:
> +1 (nb)
>
> On Mon, 20 Jul 2020 at 12:58, João Reis wrote:
>
> > +1 (nb)
> >
> > The drivers smoke test suite looks good:
> >
> >
> >
> https://ci.appveyor.com/project/DataStax/cassandra-drivers-smoke-test/builds/34194004
> >
> > Mic
+1 (binding)
On Wed, Jul 15, 2020 at 11:50 AM Joshua McKenzie
wrote:
> +1 (binding)
>
> On Wed, Jul 15, 2020 at 3:33 AM Yuji Ito wrote:
>
> > +1 (non-binding)
> >
> > Short Jepsen tests with crash injection for map, set, counter, batch, and
> > LWT passed.
> > https://github.com/scalar-labs/sca
+1 (b)
On Wed, Jun 24, 2020 at 9:59 AM Joshua McKenzie
wrote:
> A reminder: this vote will close at midnight PST today in roughly 17 hours.
>
>
> On Mon, Jun 22, 2020 at 2:20 PM J. D. Jordan
> wrote:
>
> > +1 non-binding
> >
> > > On Jun 22, 2020, at 1:18 PM, Stefan Podkowinski
> wrote:
> > >
+1
On Tue, Jun 16, 2020 at 5:37 PM Benedict Elliott Smith
wrote:
> +1
>
> On 16/06/2020, 22:23, "Nate McCall" wrote:
>
> +1 (binding)
>
> On Wed, Jun 17, 2020 at 4:19 AM Joshua McKenzie
> wrote:
>
> > Added unratified draft to the wiki here:
> >
> >
> https://cwiki.apa
Happy to lend a hand
On Mon, May 11, 2020 at 3:12 PM Eric Evans
wrote:
> I can take a turn.
>
> On Fri, May 8, 2020 at 11:10 AM Vinay Chella
> wrote:
> >
> > I would like to help as well.
> >
> >
> > On Fri, May 8, 2020 at 8:54 AM Chris Lohfink
> wrote:
> >
> > > I'd like to get involved in th
+1 to jitpack
On Fri, Apr 17, 2020 at 8:50 AM Oleksandr Petrov
wrote:
> Thank you for suggestions, Jeremiah!
>
> I first really liked the idea of jitpack since I thought it clones
> repository and builds stuff locally. However, it seems like they build on
> their machines in docker container. Wh
person's bug is another person's improvement, so it's easy for different
> perspectives to clash on this.
>
>
> On Tue, Mar 31, 2020, 3:27 PM Joseph Lynch wrote:
>
> > On Tue, Mar 31, 2020 at 1:27 PM Jake Luciani wrote:
> > >
> > > Can we agre
gs.
I'll take a deeper look at the Improvement tickets, perhaps they all fall
into this category.
Jake
On Tue, Mar 31, 2020 at 6:27 PM Joseph Lynch wrote:
> On Tue, Mar 31, 2020 at 1:27 PM Jake Luciani wrote:
> >
> > Can we agree to move the improvements out to 4.0.x?
&
I've been starting to look at the work left for 4.0 and was surprised to
see almost 1/2 the open tickets are Improvements.
Shouldn't the only criteria for 4.0 at this point should be bugs.
Can we agree to move the improvements out to 4.0.x?
-Jake
On Tue, Mar 31, 2020 at 4:02 PM Ekaterina Dimitro
Hi Ben!
Totally agree. We should collaborate on a unified operator and I think as
deployment on k8s becomes more and more prevalent we need to have
distributed testing in k8s.
To that end we are working on OSS releasing our distributed testing service
we've developed over the years to make this
nstaclustr/cassandra-operator
> (3)
> https://github.com/instaclustr/cassandra-operator/blob/master/doc/auth.md#ssl-with-sidecar
>
> On Mon, 30 Mar 2020 at 17:20, Jake Luciani wrote:
> >
> > Hello!
> > As discussed on the contributors call a couple weeks back[1], I'
Hello!
As discussed on the contributors call a couple weeks back[1], I'd like to
announce the open sourcing of a Management API Sidecar project for Apache
Cassandra that some of us have been using at Datastax[2]. It is separate
from the existing C* sidecar subproject right now as we needed specific
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)
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.
>
>
>
>
> 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
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
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
+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
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 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.
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
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
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
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 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
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
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
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
+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
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
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
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.
> > >
> &
-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.
>
>
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 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/
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
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
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.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
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
>
> 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 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
wrote:
> +1 (non-binding)
>
>
> On 2016-07-01 16:58, Jake Luciani wrote:
>
>> I propose the following artifacts for release as 2.2.7.
>>
>> sha1: 0920541
I propose the following artifacts for release as 3.0.8.
sha1: 8b21d9e9e975ea07023ae6ec4c04d997006c1a0a
Git:
http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/3.0.8-tentative
Artifacts:
https://repository.apache.org/content/repositories/orgapachecassandra-1122/org/apache
I forgot to include the test report: https://goo.gl/f78s9B
On Thu, Jun 30, 2016 at 3:30 PM, Jake Luciani wrote:
> I propose the following artifacts for release as 2.1.15.
>
> sha1: cb14186f8d6c2d1105a51e409c59a4e424958171
> Git:
> http://git-wip-us.apache.org/repos/asf?p=
I propose the following artifacts for release as 2.2.7.
sha1: 092054170ec3daf92ec494a0db295037d3563229
Git:
http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/2.2.7-tentative
Artifacts:
https://repository.apache.org/content/repositories/orgapachecassandra-1121/org/apache
I propose the following artifacts for release as 2.1.15.
sha1: cb14186f8d6c2d1105a51e409c59a4e424958171
Git:
http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/2.1.15-tentative
Artifacts:
https://repository.apache.org/content/repositories/orgapachecassandra-1118/org/apac
- tagged 3.8 for testing will send a release vote one the smoke tests
finish.
- created cassandra-3.9 branch and changed version in build.xml
- trunk build.xml now has 3.10
The Cassandra team is pleased to announce the release of Apache Cassandra
version 3.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 and
The Cassandra team is pleased to announce the release of Apache Cassandra
version 3.0.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
With 6 binding +1 and no -1 the vote passes
On Thu, Jun 9, 2016 at 4:17 AM, Gary Dusbabek wrote:
> +1
>
> On Wed, Jun 8, 2016 at 9:21 PM, Jake Luciani wrote:
>
> > I propose the following artifacts for release as 3.7.
> >
> > sha1: 6815dc970565e6cd1e
With 6 binding +1, one non-binding +1 and no -1 the vote passes
-- Forwarded message --
From: Tommy Stendahl
Date: Thu, Jun 9, 2016 at 8:40 AM
Subject: Re: [VOTE] Release Apache Cassandra 3.0.7
To: dev@cassandra.apache.org
+1 (non-binding)
On 2016-06-08 21:35, Jake Luciani
I propose the following artifacts for release as 3.0.7.
sha1: 040ac666ac5cdf9cd0a01a845f2ea0af3a81a08b
Git:
http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/3.0.7-tentative
Artifacts:
https://repository.apache.org/content/repositories/orgapachecassandra-1115/org/apache
I propose the following artifacts for release as 3.7.
sha1: 6815dc970565e6cd1e0169b5379f37da7a5a8a32
Git:
http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/3.7-tentative
Artifacts:
https://repository.apache.org/content/repositories/orgapachecassandra-1116/org/apache/cas
These releases have been tentatively frozen and tagged for testing
The Cassandra team is pleased to announce the release of Apache Cassandra
version 3.6.
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
With 6 binding +1, 6 non-binding +1 and no -1 the vote passes.
On Fri, Jun 3, 2016 at 4:02 AM, Benjamin Lerer
wrote:
> +1
>
> On Wed, Jun 1, 2016 at 7:30 PM, Jake Luciani wrote:
>
> > I propose the following artifacts for release as 3.6.
> >
> > sha1: 8d22d9fd18
Chris,
We technically do have barebones java client in tree [1]
CQL was designed as an open protocol anyone can implement [2]
We really want to see a thriving eco-system for drivers. By making CQL an
open protocol vs making it some internally controlled document/code we feel
it's the best way t
I propose the following artifacts for release as 3.6.
sha1: 8d22d9fd1842c59ea65a3793aceb5a78c5852351
Git:
http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/3.6-tentative
Artifacts:
https://repository.apache.org/content/repositories/orgapachecassandra-1114/org/apache/cas
The Cassandra team is pleased to announce the release of Apache Cassandra
version 3.0.6.
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
I've pushed a temporary cassandra-3.6 branch for the regressions found
during the vote.
ONLY regression fixes should go into that branch. Everyone else should
ignore it (*Don't* merge from 3.0-> 3.6 -> 3.7).
Regression fixes should go 3.6 -> 3.7 -> trunk
-Jake
With 6 binding +1, 6 non-binding +1 and no -1 the vote has passed.
On Thu, May 12, 2016 at 9:13 AM, Gary Dusbabek wrote:
> +1
>
> On Tue, May 10, 2016 at 8:54 PM, Jake Luciani wrote:
>
> > I propose the following artifacts for release as 3
de tests, that were
> not
> > run on previous tick-tock releases. I am re-running these tests against
> > 3.4, to confirm that suspicion.
> >
> > On Tue, May 10, 2016 at 9:54 PM, Jake Luciani wrote:
> >
> > > I propose the following artifacts for rel
I propose the following artifacts for release as 3.0.6.
sha1: 52447873a361647a5e80c547adea9cf5ee85254a
Git:
http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/3.0.6-tentative
Artifacts:
https://repository.apache.org/content/repositories/orgapachecassandra-1110/org/apache
I propose the following artifacts for release as 3.6.
sha1: c17cbe1875a974a00822ffbfad716abde363c8da
Git:
http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/3.6-tentative
Artifacts:
https://repository.apache.org/content/repositories/orgapachecassandra-1112/org/apache/cas
I've tagged 3.6 and 3.0.6 tentatively for release. This means all changes
to this version are effectively frozen barring a regression in the tagged
version.
I've created cassandra-3.7 branch and marked the build version as such.
Trunk is now marked 3.8.
New JIRA versions for 3.7 and 3.0.7 and 3.8
The Cassandra team is pleased to announce the release of Apache Cassandra
version 2.2.6.
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.1.14.
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
With 5 binding +1, 1 non-binding +1 and no -1 the vote passes
On Fri, Apr 22, 2016 at 5:12 PM, Jake Luciani wrote:
>
> I propose the following artifacts for release as 2.1.14.
>
> sha1: 209ebd380b641c4f065e9687186f546f8a50b242
> Git:
> http://git-wip-us.apache.org/repos/asf
With 5 binding +1, 1 non-binding +1 and no -1 the vote passes
On Fri, Apr 22, 2016 at 5:15 PM, Jake Luciani wrote:
>
> I propose the following artifacts for release as 2.2.6.
>
> sha1: 37f63ecc5d3b36fc115fd7ae98e4fc1f4bc2d1d6
> Git:
> http://git-wip-us.apache.org/repos/asf
Just a reminder I will be tagging 3.6 for tagging EOD next monday.
I propose the following artifacts for release as 2.2.6.
sha1: 37f63ecc5d3b36fc115fd7ae98e4fc1f4bc2d1d6
Git:
http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/2.2.6-tentative
Artifacts:
https://repository.apache.org/content/repositories/orgapachecassandra-1108/org/apache
I propose the following artifacts for release as 2.1.14.
sha1: 209ebd380b641c4f065e9687186f546f8a50b242
Git:
http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/2.1.14-tentative
Artifacts:
https://repository.apache.org/content/repositories/orgapachecassandra-1109/org/apac
The Cassandra team is pleased to announce the release of Apache Cassandra
version 3.5.
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
With 6 binding +1, 3 non-binding +1 and no -1 the vote passes.
On Mon, Apr 11, 2016 at 11:47 AM, Josh McKenzie
wrote:
> +1
>
> On Sun, Apr 10, 2016 at 11:43 AM, Jake Luciani wrote:
>
> > I propose the following artifacts for release as
The Cassandra team is pleased to announce the release of Apache Cassandra
version 3.0.5.
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
With 6 binding +1 and 3 non binding +1 the and no -1 the vote passes.
I will publish
On Fri, Apr 8, 2016 at 12:41 PM, Josh McKenzie wrote:
> +1
>
> On Thu, Apr 7, 2016 at 6:10 PM, Jake Luciani wrote:
>
> > I propose the following artifacts for release as 3
I propose the following artifacts for release as 3.5.
sha1: 020dd2d1034abc5c729edf1975953614b33c5a8b
Git:
http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/3.5-tentative
Artifacts:
https://repository.apache.org/content/repositories/orgapachecassandra-1106/org/apache/cas
>
> > > >> > > So it's a new regression, not present in 3.4?
> > > >> > >
> > > >> > > On Thu, Apr 7, 2016 at 5:24 PM, Pavel Yaskevich <
> > pove...@gmail.com>
> > > >> > wrote:
> > >
I propose the following artifacts for release as 3.5.
sha1: 89bd93502ac141f8cd13f8738bb4314488db2a5a
Git:
http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/3.5-tentative
Artifacts:
https://repository.apache.org/content/repositories/orgapachecassandra-1105/org/apache/cas
I propose the following artifacts for release as 3.0.5.
sha1: c6e6fa94d28c0d23a8154e3743c05b355dba710a
Git:
http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/3.0.5-tentative
Artifacts:
https://repository.apache.org/content/repositories/orgapachecassandra-1104/org/apache
The Cassandra team is pleased to announce the release of Apache Cassandra
version 3.4.
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
1 - 100 of 335 matches
Mail list logo
