Re: Should we change 4.1 to G1 and offheap_objects ?

On 1/13/23 05:50, Mick Semb Wever wrote: Thanks for the support Brad, you're definitely not alone. Alas the project works in a consensus model, i.e. off the objections made - which have been all sound. A good compromise has been offered that I will move forward on, and I'll also update the comm

Re: [VOTE] CEP-30 ANN Vector Search

+1, this is cool. On 5/25/23 10:45, 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

Re: [VOTE] CEP-8 Datastax Drivers Donation

+1 On 6/13/23 09:14, 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 is in favor of the donation. Nothing more. The plan is to introduce the drivers, one by

Re: [VOTE] Accept java-driver

+1 (late to the vote, but wanted to publicly note my support) Kind regards, Michael On 10/2/23 23:52, Mick Semb Wever wrote: The donation of the java-driver is ready for its IP Clearance vote. https://incubator.apache.org/ip-clearance/cassandra-java-driver.html

Re: Plans for switching to logback 1.3.x/1.4.x?

Although I have not searched jira, I'd bet plans could use help, if they exist. I recall the jog4j -> logback transition, and it was not super complex, and reading through the logback docs, some defaults were updated and the project gained a nice feature bump. I would think a minor version rev

Re: CI's working, and repeatable !!

💯! Amazing work - thanks so much for posting the details, Mick, and Josh is right on. Kinda bummed I haven't been following C* CI dev, being more on the ops side lately. Posting this up has me intrigued, so I may just have to go poke around some and scratch an itch :) Warm regards, Michael On Su

Re: [VOTE] CEP-24 Password validation / generation

+1 Michael On 6/17/24 04:32, Štefan Miklošovič wrote: Hi everyone, I would like to start the voting for CEP-24 as all feedback in the discussion threads seem to be addressed. Proposal: https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=228494146

Re: [VOTE][IP CLEARANCE] GoCQL driver

+1 Kind regards, Michael On 6/25/24 12:29, Mick Semb Wever wrote: Please vote on the acceptance of the GoCQL driver and its IP Clearance: https://incubator.apache.org/ip-clearance/cassandra-gocql-driver.html All consent

Re: Hi-Rez of Apache Cassandra logo??

Nice, thanks! I went ahead and committed the files to SVN. I hope that was OK, Scott :) https://svn.apache.org/repos/asf/cassandra/logo/ r1831825 | mshuler | 2018-05-18 00:53:54 -0500 (Fri, 18 May 2018) | 5 lines Add Apac

Re: 3.11.3

+1 for all the active branches. It will also be a good chance to review the release doc addition Mick so graciously wrote up. https://github.com/apache/cassandra/pull/230 -- Michael On 06/06/2018 07:30 AM, Jason Brown wrote: wrt releasing 3.11, +1 to this ... and additionally, 3.0 and 2.2. I'

Re: Small improvement on website

On 06/13/2018 02:50 PM, Roy Lenferink wrote: Hi folks, Yesterday I got a message through the Apache Software Foundation Facebook page containing a small point of feedback. It's about a missing space after a period, on the index.html page of the website: "mission-critical data.Cassandra's..." T

[VOTE] Release Apache Cassandra 2.2.13

I propose the following artifacts for release as 2.2.13. sha1: 9ff78249a0a5e87bd04bf9804ef1a3b29b5e1645 Git: http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/2.2.13-tentative Artifacts: https://repository.apache.org/content/repositories/orgapachecassandra-1159/org/a

[VOTE] Release Apache Cassandra 3.0.17

I propose the following artifacts for release as 3.0.17. sha1: c4e6cd2a1aca84a88983192368bbcd4c8887c8b2 Git: http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/3.0.17-tentative Artifacts: https://repository.apache.org/content/repositories/orgapachecassandra-1160/org/a

[VOTE] Release Apache Cassandra 3.11.3

I propose the following artifacts for release as 3.11.3. sha1: aed1b5fdf1e953d19bdd021ba603618772208cdd Git: http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/3.11.3-tentative Artifacts: https://repository.apache.org/content/repositories/orgapachecassandra-1161/org/a

[VOTE FAILED] Release Apache Cassandra 3.11.3

> effect on streaming is verified. The concern is that the snitch change > could make cross DC streaming more likely. I’ve opened CASSANDRA-14555 for > this. > > > On 3 July 2018 at 04:02, Nate McCall wrote: > >> +1 >> >> On Tue, Jul 3, 2018 at 8:11 AM, Mi

[VOTE FAILED] Release Apache Cassandra 3.0.17

> effect on streaming is verified. The concern is that the snitch change > could make cross DC streaming more likely. I’ve opened CASSANDRA-14555 for > this. > > > On 3 July 2018 at 04:02, Nate McCall wrote: > >> +1 >> >> On Tue, Jul 3, 2018 at 8:10 AM, Mi

[VOTE FAILED - VETO] Release Apache Cassandra 2.2.13

yay for the test results analyzer not working. > > On 4 July 2018 at 09:06, Stefan Podkowinski wrote: > >> +1 >> >> On 02.07.2018 22:10, Michael Shuler wrote: >>> I propose the following artifacts for release as 2.2.13. >>> >>> sha1: 9ff78249a

Re: [VOTE] Branching Change for 4.0 Freeze

+0 There are pros and cons. I do hope the pros work out and the cons aren't too impactful. I thought about just abstaining, but figured a "meh, whatever" vote was at least worth voicing. Michael On 07/11/2018 04:46 PM, sankalp kohli wrote: > Hi, > As discussed in the thread[1], we are propos

Re: reroll the builds?

On 07/16/2018 11:27 PM, Jason Brown wrote: > Hey all, > > The recent builds were -1'd, but it appears the issues have been resolved > (2.2.13 with CASSANDRA-14423, and 3.0.17 / 3.11.3 reverting > CASSANDRA-14252). Can we go ahead and reroll now? Could someone run through the tests on 2.2, 3.0, 3.

[VOTE] Release Apache Cassandra 3.11.3 (Take 2)

I propose the following artifacts for release as 3.11.3. sha1: 31d5d870f9f5b56391db46ba6cdf9e0882d8a5c0 Git: http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/3.11.3-tentative Artifacts: https://repository.apache.org/content/repositories/orgapachecassandra-1164/org/apac

[VOTE] Release Apache Cassandra 3.0.17 (Take 2)

I propose the following artifacts for release as 3.0.17. sha1: d52c7b8c595cc0d06fc3607bf16e3f595f016bb6 Git: http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/3.0.17-tentative Artifacts: https://repository.apache.org/content/repositories/orgapachecassandra-1165/org/apac

[VOTE] Release Apache Cassandra 2.2.13

I propose the following artifacts for release as 2.2.13. sha1: 3482370df5672c9337a16a8a52baba53b70a4fe8 Git: http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/2.2.13-tentative Artifacts: https://repository.apache.org/content/repositories/orgapachecassandra-1167/org/apac

Re: [VOTE] Release Apache Cassandra 2.2.13

With 9 binding +1, 2 non-binding +1, and no other votes, this vote passed. I'll get the artifacts uploaded as soon as I can. -- Warm regards, Michael On 07/25/2018 12:17 AM, Michael Shuler wrote: > I propose the following artifacts for release as 2.2.13. &

Re: [VOTE] Release Apache Cassandra 3.0.17 (Take 2)

With 9 binding +1, 3 non-binding +1, and no other votes, this vote passed. I'll get the artifacts uploaded as soon as I can. -- Warm regards, Michael On 07/25/2018 12:17 AM, Michael Shuler wrote: > I propose the following artifacts for release as 3.0.17. &

Re: [VOTE] Release Apache Cassandra 3.11.3 (Take 2)

With 9 binding +1, 4 non-binding +1, and no other votes, this vote passed. I'll get the artifacts uploaded as soon as I can. -- Warm regards, Michael On 07/25/2018 12:16 AM, Michael Shuler wrote: > I propose the following artifacts for release as 3.11.3. &

[RELEASE] Apache Cassandra 2.2.13 released

The Cassandra team is pleased to announce the release of Apache Cassandra version 2.2.13. 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

[RELEASE] Apache Cassandra 3.0.17 released

The Cassandra team is pleased to announce the release of Apache Cassandra version 3.0.17. 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

[RELEASE] Apache Cassandra 3.11.3 released

The Cassandra team is pleased to announce the release of Apache Cassandra version 3.11.3. 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

Re: Side Car New Repo vs not

+1 for a separate repository. Michael On 08/23/2018 07:30 PM, Murukesh Mohanan wrote: > FWIW, I think it's possible to merge in a separate repository into a > subdirectory while keeping git history, but I don't know if the other way > will be possible if commits span other parts of the repo as we

FYI: builds.apache.org is down

https://status.apache.org/ https://lists.apache.org/thread.html/53e9cf7ded15f2e348be2fd36a11fd3aa4dc43462d6aa5a197dbd337@%3Cbuilds.apache.org%3E -- Kind regards, Michael - To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache

Re: [Discuss] Accept GoCQL driver donation

On 08/31/2018 09:34 AM, Jay Zhuang wrote: > That's great. Could that be in the same repo as Cassandra or a > separate repo? For similar reasons as discussed for an admin tool, separate repositories are quick and simple to create, as well as allow handling contribution, CI, build, release, etc. mec

Re: [Discuss] Accept GoCQL driver donation

On 08/31/2018 05:20 PM, Brandon Williams wrote: > On Fri, Aug 31, 2018 at 4:24 PM Gary Dusbabek wrote: > >> At what point is the project comfortable/trusting with granting commit bits >> to someone who is very familiar with a facet of the project (say, a go >> client, or dtests), but hasn't made

Re: Request for post-freeze merge exception

+1 to merge. -- Michael On 09/04/2018 01:05 PM, Sam Tunnicliffe wrote: > Hey all, > > On 2018-31-08 CASSANDRA-14145 had been +1'd by two reviewers and CI was > green, and so it was marked Ready To Commit. This was before the 4.0 > feature freeze but before it landed, CASSANDRA-14408, which touc

Re: Moving tickets out of 4.0 post freeze

On 9/24/18 7:09 AM, Joshua McKenzie wrote: > I propose we move all new features and improvements to 4.0.x to keep the > surface area of change for the major stable. It occurs to me that we should probably update the version in trunk to 4.0.0, if we're following semantic versions. I suppose this al

Re: Moving tickets out of 4.0 post freeze

ere >>> treated as majors for EOL'ing support for older releases. This >>> must surely have been confusing for users, and I’m not sure what >>> we got from it? >>> >>> Why don’t we keep it simple, and just have major.patch? So we >>> woul

Re: CASSANDRA-13241 lower default chunk_length_in_kb

On 10/19/18 9:16 AM, Joshua McKenzie wrote: > > At the risk of hijacking this thread, when are we going to transition from > "no new features, change whatever else you want including refactoring and > changing years-old defaults" to "ok, we think we have something that's > stable, time to start te

Re: Cassandra 4.0 on Windows 10 crashing upon startup with Java 11

On 11/12/18 4:01 AM, Steinmaurer, Thomas wrote: > Hello, > > on Windows 10, Cassandra 4.0 (trunk Nov 12) is crashing upon startup with > Java 11, SIGAR related. Startup with Java8 works fine. Is this a known issue? > > First part of the hs_err_pid file. > > # > # A fatal error has been detected

Re: RES: Implicit Casts for Arithmetic Operators

On 11/20/18 9:53 AM, Versátil wrote: > > PLEASE TAKE MY EMAIL FROM THIS SHIT !! FYI, mailing list subscriptions (and unsubscriptions) are self-serve. In general, you subscribed yourself, so you are responsible to unsubscribe. The email address to do so is appended to every plain text message to t

Re: RES: RES: Implicit Casts for Arithmetic Operators

On 11/20/18 10:15 AM, Versátil wrote: > > I already requested as you said and it did not help. And I NEVER asked to > enter into this discussion. Please request to withdraw my email | | | | | | | | | | \/\/\/\/\/\/\/\/\/\/ > > -

Re: [VOTE] Change Jira Workflow

+1 -- Michael On 12/17/18 9:19 AM, Benedict Elliott Smith wrote: > I propose these changes > * > to the Jira Workflow for the project. The vote will be open for 72 hours**. > > I am, of course, +1. > > * With the

Re: Git Repo Migration

This change will be forced on Feb 7, so a vote isn't really relevant :) I'm in favor of sooner is better. Things are relatively quiet right now, post-holidays. Let's do it Monday, for example, and we can work through the config changes while most people are fresh from a break. The longer we wait,

Re: Git Repo Migration

way. I was just going to give a few days for people to chime in about >> timings, seeing as some may still be afk after holidays etc. I’ll give it a >> little while to at least maintain the illusion of waiting for consensus, >> but filing the JIRA early next week SGTM. >>

Re: Who should be in our distribution KEYS file?

Mick and I have discussed this previously, but I don't recall if it was email or irc. Apologies if I was unable to describe the problem to a point of general understanding. To reiterate the problem, changing gpg signature keys screws our debian and redhat package repositories for all users. Tarbal

Re: Who should be in our distribution KEYS file?

14963. Michael On 1/7/19 3:15 PM, Michael Shuler wrote: > Mick and I have discussed this previously, but I don't recall if it was > email or irc. Apologies if I was unable to describe the problem to a > point of general understanding. > > To reiterate the problem, changing g

Re: Who should be in our distribution KEYS file?

rg%3E Michael On 1/7/19 3:32 PM, Michael Shuler wrote: > To-do items that might further the goal of getting more people involved > in releases, here are a couple tickets on this: > > https://issues.apache.org/jira/browse/CASSANDRA-14962 > https://issues.apache.org/jira/browse/CASSANDRA-

Re: Who should be in our distribution KEYS file?

point is that requesting a release from a >> static release manager is a sign of a flaw in the release process. >> >> On a human, note, it feels a little awkward asking for a release. I might >> be alone on this though. >> >> Jon >> >> >>

Re: [DISCUSS] releasing next 3.0 & 3.11

No problem, thanks for asking :) Michael On 1/7/19 6:20 PM, Jonathan Haddad wrote: > It's been 5 months and 30+ bug fixes to each branch. > > Here's the two changelogs: > > https://github.com/apache/cassandra/blob/cassandra-3.0/CHANGES.txt > https://github.com/apache/cassandra/blob/cassandra-3.

EOL 2.1 series?

It came to my attention on IRC a week or so ago, and following up on the ticket that someone asked if they should commit to 2.1, that developers have been actively ignoring the 2.1 branch. If we're not committing critical fixes there, even when we know they exist, I think it's time to just call it

Re: Who should be in our distribution KEYS file?

; would be the ideal way of creating and distributing package, i.e. having > a Debian/Fedora/Ubuntu maintainer taking care of that and only have > users come back to us for the vanilla rpm in case their downstream > version is outdated. > > > On 08.01.19 02:48, Michael Shuler wrote: &

Re: Who should be in our distribution KEYS file?

one key change for deb/rpm repository users. Michael On 1/9/19 11:13 AM, Michael Shuler wrote: > For Debian, Fedora, etc. to package Cassandra at the OS level, first all > dependencies (and deps of deps) must be packaged and uploaded, so they > can be depended on by Cassandra. This means H

Re: [DISCUSS] releasing next 3.0 & 3.11

On 1/16/19 1:05 PM, Jonathan Haddad wrote: > Ping on this. https://issues.apache.org/jira/browse/CASSANDRA-14970 I could just punt and use what we've got with md5,sha1 checksums, then toss sha256,sha512 checksums in dist repo, when we're done. It's not pretty, but would work for me. That method w

[VOTE] Release Apache Cassandra 2.2.14

I propose the following artifacts for release as 2.2.14. sha1: af91658353ba601fc8cd08627e8d36bac62e936a Git: https://gitbox.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/2.2.14-tentative Artifacts: https://repository.apache.org/content/repositories/orgapachecassandra-1172/org/apache/

[VOTE] Release Apache Cassandra 3.0.18

I propose the following artifacts for release as 3.0.18. sha1: edd52cef50a6242609a20d0d84c8eb74c580035e Git: https://gitbox.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/3.0.18-tentative Artifacts: https://repository.apache.org/content/repositories/orgapachecassandra-1171/org/apache/

[VOTE] Release Apache Cassandra 2.1.21

*EOL* release for the 2.1 series. There will be no new releases from the 'cassandra-2.1' branch after this release. I propose the following artifacts for release as 2.1.21. sha1: 9bb75358dfdf1b9824f9a454e70ee2c02bc64a45 Git: https://gitbox.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=r

[VOTE] Release Apache Cassandra 3.11.4

I propose the following artifacts for release as 3.11.4. sha1: fd47391aae13bcf4ee995abcde1b0e180372d193 Git: https://gitbox.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/3.11.4-tentative Artifacts: https://repository.apache.org/content/repositories/orgapachecassandra-1170/org/apache/

Re: [VOTE] Release Apache Cassandra 2.1.21

; these other votes we have up right now). >>> >>> I don't feel the need to be absolutist about something being EOL. >>> >>> On Sun, Feb 3, 2019 at 1:47 AM Stefan Podkowinski >> wrote: >>>> >>>> What are we voting on here? Releasing the 2.1

Re: [VOTE PASSED] Release Apache Cassandra 3.11.4

I count 8 binding +1 votes, 3 non-binding +1's, and no other votes, so this vote passes. I'll get the artifacts published as soon as I can. Kind regards, Michael On 2/2/19 6:31 PM, Michael Shuler wrote: > I propose the following artifacts for release as 3.11

Re: [VOTE PASSED] Release Apache Cassandra 3.0.18

With 8 binding +1 votes, 3 non-binding +1's, and no other votes, this vote passed. I'll publish artifacts as soon as I can. Kind regards, Michael On 2/2/19 6:32 PM, Michael Shuler wrote: > I propose the following artifacts for release as 3.0.

Re: [VOTE PASSED] Release Apache Cassandra 2.2.14

With 7 binding +1 votes, 2 non-binding +1, and no others, this vote passed. I'll upload the artifacts as soon as possible. Kind regards, Michael On 2/2/19 6:32 PM, Michael Shuler wrote: > I propose the following artifacts for release as 2.2.14. > > sha1: af91658353ba601fc8cd08627e

Re: [VOTE] Release Apache Cassandra 2.1.21

/2/19 6:32 PM, Michael Shuler wrote: > *EOL* release for the 2.1 series. There will be no new releases from the > 'cassandra-2.1' branch after this release. > > > > I propose the following artifacts for release as 2.1.21. > > sha1: 9bb75358dfd

[RELEASE] Apache Cassandra 3.11.4 released

The Cassandra team is pleased to announce the release of Apache Cassandra version 3.11.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 a

[RELEASE] Apache Cassandra 3.0.18 released

The Cassandra team is pleased to announce the release of Apache Cassandra version 3.0.18. 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

[RELEASE] Apache Cassandra 2.2.14 released

The Cassandra team is pleased to announce the release of Apache Cassandra version 2.2.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

[RELEASE] Apache Cassandra 2.1.21 released

The Cassandra team is pleased to announce the release of Apache Cassandra version 2.1.21. 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

Re: CASSANDRA-14482

+0.5 I skimmed the jira and github diff and a few things came to mind: - There are multiple comments about using an older jar than the latest version. - I did not see any performance test results to form an opinion on any gains/caveats as a user. This was the first thing I looked for. - I did not

Re: Looking for common cases in cassandra fit to autoheal

Your request is not related to the topic of this mailing list, the development of Apache Cassandra. Your question would be better suited for the user@ mailing list. Your question is also quite vague, and you might include some detail or context about what exactly you are looking for. You may also w

Re: Both Java 8 and Java 11 required for producing a tarball

On 3/6/19 7:10 PM, Stefan Miklosovic wrote: > I am trying to build 4.0 from sources and prior to this I was doing > > ant artifacts > > in order to get distribution tarball to play with. > > If I understand this right, if I do not run Ant with Java 11, > java.version.8 will be true so it will sk

Re: Cassandra repo keys are revoked

revoked > keys. > > apt-key list > > > pub rsa4096 2014-06-16 [SCEA] [revoked: 2016-08-16] > 7B0A 593A 9795 A964 AD57 D255 D46C 5ECB FE4B 2BDA > uid [ revoked] Michael Shuler > > pub rsa4096 2009-07-15 [SC] > A26E 528B 271F 19B9 E5D8

Re: Cassandra repo keys are revoked

On 3/11/19 2:41 PM, Michael Shuler wrote: > On 3/11/19 8:36 AM, staticp...@gmail.com wrote: >> Hello, >> >> It appears the keys listed here are outdated. >> https://www.apache.org/dist/cassandra/KEYS >> >> Trying to install Casandra 311x on Ubuntu 18.0.4. Th

Re: Choosing a supported Python 3 major version for cqlsh

On 3/18/19 9:06 PM, Patrick Bannister wrote: > I recommend we pick the longest supported stable release available. That > would be Python 3.7, which is planned to get its last release in 2023, four > years from now. > - Python 3.5 was planned to get its last major release yesterday > - Python 3.6 i

Re: Choosing a supported Python 3 major version for cqlsh

On 3/18/19 9:52 PM, Michael Shuler wrote: > On 3/18/19 9:06 PM, Patrick Bannister wrote: >> I recommend we pick the longest supported stable release available. That >> would be Python 3.7, which is planned to get its last release in 2023, four >> years from now. >> - Py

"4.0: TBD" -> "4.0: Est. Q4 2019"?

We've had 4.0 listed as TBD release date for a very long time. Yesterday, Alexander Dejanovski got a "when's 4.0 going to release?" question after his repair talk and he suggested possibly Q4 2019. This morning Nate McCall hinted at possibly being close by ApacheCon Las Vegas in September. The

Re: Time for a new 3.0/3.11 release?

On 7/1/19 3:32 PM, Blake Eggleston wrote: Any objections to doing a new 3.0 and 3.11 release? Both branches have accumulated a decent number of changes since their last release, the highlights being improved merkle tree footprint, a gossip race, and a handful of 2.1 -> 3.x upgrade bugs. I was l

Re: Time for a new 3.0/3.11 release?

On 7/3/19 1:44 PM, aj...@apache.org wrote: In fact there is a branch for it noted in the ticket, from which a patch could be cut instantly, but there doesn't seem to be any point to doing that until the feature freeze is over. Is there any sense of timing on that? I've seen a few discussions abou

Request for review - 2 jiras for 3.0/3.11

Resending as a new req-for-review thread for visibility, since they look important to my untrained eye: https://issues.apache.org/jira/browse/CASSANDRA-15097 https://issues.apache.org/jira/browse/CASSANDRA-15098 Michael Forwarded Message Subject: Re: Time for a new 3.0/3.11 r

Re: Isn't there a workable cassandra java source for developing as other big data system?

You have a dirty build environment. Your path of "/cassandra-trunk/src" in the error and the suggestion on slack that you are trying to build cassandra-3.11.3 shows me you need to start over fresh. Here you go: build docs: http://cassandra.apache.org/doc/latest/development/ide.html build steps

Re: Apache Cassandra Virtual meetings

On 8/19/19 3:40 PM, Dinesh Joshi wrote: shared Google Calendar This. I adore simple gcal additions and use quite a few. Thanks for the suggestion! I would also, selfishly, love to get some folks actively posting things to #cassandra-dev during NGCC/ApacheCon, since I cannot attend. I'll be

Re: Contributing cassandra-diff

CI git polling for changes on a separate repository (if/when CI is needed) is probably a better way to go. I don't believe there are any issues with INFRA on us having discrete repos, and creating them with the self-help web tool is quick and easy. Thanks for the neat looking utility! Michael

Re: Stability of MaterializedView in 3.11.x | 4.0

It appears that you found the first message of the chain. I suggest reading the linked JIRA and the complete dev@ thread that arrived at this conclusion; there are loads of well formed opinions and information. Users of MVs *must* determine for themselves, through thorough testing and understan

Re: 4.0 alpha before apachecon?

Thanks for the reminder :) I have a few days of availability to prep a 4.0 alpha release. It's an alpha, so I don't have a problem with known issues needing work. I will have an internet-less period of time starting roughly Tuesday 9/3 through about Friday 9/13. I might get lucky and have a li

Re: Builds email notifications

On 9/4/19 8:33 AM, Mick Semb Wever wrote: Jenkins does have this functionality: with "E-mail Notification" configuration under the "Post-build Actions" section. Emails are sent when a build fails, becomes unstable or returns to stable, to a specified ML and the authors of the breakage. Is t

Re: Builds email notifications

On 9/4/19 9:01 AM, Mick Semb Wever wrote: This is going to be a job('Cassandra-template-artifacts') {publishers ...} step in the template, if I recall. Not sure what email plugins are installed. I'd be happy to look at a PR. Quick or the dead around here :-) It has been done manually, an

Re: 4.0 alpha before apachecon?

?jql=project%20%3D%20CASSANDRA%20AND%20fixVersion%20%3D%204.0-alpha [3] https://issues.apache.org/jira/issues/?jql=project%20%3D%20CASSANDRA%20AND%20fixVersion%20%3D%204.0-beta What do people think? -Joey On Wed, Aug 28, 2019 at 10:58 AM Michael Shuler wrote: Thanks for the reminder :) I have

[VOTE] Release Apache Cassandra 4.0-alpha1 (24 hour vote)

I propose the following artifacts for release as 4.0-alpha1. sha1: fc4381ca89ab39a82c9018e5171975285cc3bfe7 Git: https://gitbox.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/4.0-alpha1-tentative Artifacts: https://repository.apache.org/content/repositories/orgapachecassandra-1177/

Re: [VOTE] Release Apache Cassandra 4.0-alpha1 (24 hour vote)

NEWS.txt link was incorrect (fixed in template for next time). https://gitbox.apache.org/repos/asf?p=cassandra.git;a=blob_plain;f=NEWS.txt;hb=refs/tags/4.0-alpha1-tentative -- Michael On 9/5/19 3:44 PM, Michael Shuler wrote: I propose the following artifacts for release as 4.0-alpha1. sha1

Re: [VOTE] Release Apache Cassandra 4.0-alpha1 (24 hour vote)

ep 5, 2019 at 3:55 PM Jon Haddad wrote: +1 On Thu, Sep 5, 2019 at 3:44 PM Michael Shuler wrote: I propose the following artifacts for release as 4.0-alpha1. sha1: fc4381ca89ab39a82c9018e5171975285cc3bfe7 Git: https://gitbox.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/4.0-a

[VOTE PASSED] Release Apache Cassandra 4.0-alpha1 (24 hour vote)

4.0-alpha1 vote successful. I will get the artifacts published as soon as I can. -- Kind regards, Michael On 9/5/19 3:44 PM, Michael Shuler wrote: I propose the following artifacts for release as 4.0-alpha1. sha1: fc4381ca89ab39a82c9018e5171975285cc3bfe7 Git: https://gitbox.apache.org/r

[RELEASE] Apache Cassandra 4.0-alpha1 released

The Cassandra team is pleased to announce the release of Apache Cassandra version 4.0-alpha1. 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

Re: moving the site from SVN to git

I see no good reason to trash history. There are tools to make moving from svn to git (hopefully) painless. We used git-svn for the main c* source to retain history of both, which this tool uses to do migrations - https://github.com/nirvdrum/svn2git Michael On 9/25/19 12:57 AM, Mick Semb Weve

Re: moving the site from SVN to git

tomorrow with more storage to see if I get a better result. Mick if you want to give it a shot in the meantime that would be appreciated. Jon On Wed, Oct 2, 2019 at 3:18 PM Jon Haddad wrote: I created an INFRA ticket here: https://issues.apache.org/jira/browse/INFRA-19218. On Wed, Sep 25,

Re: moving the site from SVN to git

king a look, Michael. Hopefully you have better luck than me :) On Thu, Oct 3, 2019 at 6:42 AM Michael Shuler wrote: I cloned the empty cassandra-website git repo, and I'm running: svn2git http://svn.apache.org/repos/asf/cassandra/site --rootistrunk --no-minimize-url ..to see what I get. An

Re: moving the site from SVN to git

committed! :) https://gitbox.apache.org/repos/asf?p=cassandra-website.git Michael On 10/3/19 12:22 PM, Jon Haddad wrote: I think we can safely ignore them. Thanks for figuring this out. On Thu, Oct 3, 2019 at 10:01 AM Michael Shuler wrote: I'm making progress through many per

Re: Can we kick off a release?

Will do! I probably won't get this done this evening, so will send out the emails tomorrow. Thanks, Michael On Mon, Oct 7, 2019 at 2:37 PM Jon Haddad wrote: > > Michael, > > Would you mind kicking off builds and starting a vote thread for the latest > 2.2, 3.0 and 3.11 builds? > > Much appreciat

Re: Can we kick off a release?

I add a cqlsh test > and merge it, that’d be good. > > Thanks, > Sam > > > On 7 Oct 2019, at 22:54, Michael Shuler wrote: > > > > Will do! I probably won't get this done this evening, so will send out > > the emails tomorrow. > > > > Thanks

Re: [VOTE-2] Apache Cassandra Release Lifecycle

+1 -- Kind regards, Michael On Wed, Oct 9, 2019 at 9:06 AM Aleksey Yeshchenko wrote: > > +1 as a rather reasonable starting point; we can make changes to the process > in the future if need be. > > > On 8 Oct 2019, at 19:00, sankalp kohli wrote: > > > > Hi, > >We have discussed in the ema

Re: Improving our frequency of (patch) releases, and letting committers make releases

Noted: https://issues.apache.org/jira/browse/CASSANDRA-14963 Fundamental current docker build flaws: https://issues.apache.org/jira/browse/CASSANDRA-14962 Distribution changes suggested for deb/rpm: https://issues.apache.org/jira/browse/CASSANDRA-14966 https://issues.apache.org/jira/browse/CASSA

Re: Improving our frequency of (patch) releases, and letting committers make releases

Oh! As an added bonus of migrating to proper bintray package repository types, we also cure the pain of users attempting to install older versions than the latest release, since all versions in the suite are installable. -- Michael On 10/17/19 9:47 AM, Michael Shuler wrote: Noted: https

[VOTE] Release Apache Cassandra 2.2.15

I propose the following artifacts for release as 2.2.15. sha1: 4ee4ceea28a1cb77b283c7ce0135340ddff02086 Git: https://gitbox.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/2.2.15-tentative Artifacts: https://repository.apache.org/content/repositories/orgapachecassandra-1179/org/apac

[VOTE] Release Apache Cassandra 3.11.5

I propose the following artifacts for release as 3.11.5. sha1: b697af87f8e1b20d22948390d516dba1fbb9eee7 Git: https://gitbox.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/3.11.5-tentative Artifacts: https://repository.apache.org/content/repositories/orgapachecassandra-1184/org/apac

[VOTE] Release Apache Cassandra 4.0-alpha2

I propose the following artifacts for release as 4.0-alpha2. sha1: ca928a49c68186bdcd57dea8b10c30991c6a3c55 Git: https://gitbox.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/4.0-alpha2-tentative Artifacts: https://repository.apache.org/content/repositories/orgapachecassandra-1185/

  1   2   3   4   5   >