Re: [VOTE] Release Apache Cassandra 5.0-rc1 (take3)

+1 (we're off rhel7, woot!) On 7/17/24 15:20, Mick Semb Wever wrote: On Wed, 17 Jul 2024 at 21:40, Brandon Williams > wrote: On Wed, Jul 17, 2024 at 2:36 PM Mick Semb Wever mailto:m...@apache.org>> wrote: > > Should we remove the noboolean rpm from the

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

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: 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

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: [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: [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] 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: 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

Re: Dropping Python 3.6 support in 4.1

This. RHEL8 is going to be around for a long while, so I'd say python-3.6 should not be dropped for a long while. 2029 EOL is the date I see on the RHEL8 Planning Guide[0].. I saw the RHEL7/CentOS7 comments earlier and immediately thought about RHEL8 and python-3.6, since I'm working in that

Re: [VOTE] CEP-19: Trie memtable implementation

+1 On 2/16/22 02:57, Branimir Lambov wrote: Hi everyone, I'd like to propose CEP-19 for approval. Proposal: https://cwiki.apache.org/confluence/display/CASSANDRA/CEP-19%3A+Trie+memtable+implementation

Re: [VOTE] Formalizing our CI process

(still) +1 as amended Michael On 1/12/22 11:54, Caleb Rackliffe wrote: +1 w/ Joey's amendment On Wed, Jan 12, 2022 at 11:04 AM Joshua McKenzie > wrote: I'd say an amendment with a directional poll would be fine. I don't think this is controversial.

Re: [VOTE] Formalizing our CI process

+1 Michael On 1/10/22 13:00, Joshua McKenzie wrote: Wiki draft article here: https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=199530280 The vote will be open for 72 hours (it's short + early

Re: unable to connect to apache ccassandra

Reply-to set to user@ mailing list address, which would the best place to seek this type of help; dev@ bcc'ed. Is cassandra running, did you start it? Is the process listening on localhost (127.0.0.1) port 9042? `ss -ltn | grep 9042` would be a good way to check if the process is listening.

Re: [VOTE] CEP-3: Guardrails

+1 Kind regards, Michael Shuler On 11/11/21 5:29 AM, Andrés de la Peña wrote: Hi everyone, I would like to start a vote on this CEP. Proposal: https://cwiki.apache.org/confluence/display/CASSANDRA/CEP-3%3A+Guardrails Discussion: https://lists.apache.org/thread

Re: Cassandra site broken links

rep '^\sid #' c*.log.txt |wc -l 1416 $ egrep '^\s4' c*.log.txt |wc -l 55 $ egrep '^\slookup' c*.log.txt |wc -l 20 $ egrep '^\stimeout' c*.log.txt |wc -l 1 Warm regards, Michael On 11/6/21 11:59 AM, Michael Shuler wrote: FYI - I'm going to try to slow down the checks, since I just noticed a bunch

Re: Cassandra site broken links

FYI - I'm going to try to slow down the checks, since I just noticed a bunch of the 4xx errors are "HTTP 429 Too Many Requests" Kind regards, Michael On 11/6/21 11:52 AM, Michael Shuler wrote: (Sending to dev@ which seems a better place to discuss; updated subject. Thanks OP

Cassandra site broken links

(Sending to dev@ which seems a better place to discuss; updated subject. Thanks OP!) I ran a couple link checking tools on the site and there are lots more problems than the couple noted. This seems like a good task for a non-dev to make a substantial project impact. Muffet [0] seemed the

Re: [VOTE] CEP-15: General Purpose Transactions

1. +1 2. +1 3. +1 On 10/14/21 11:31 AM, bened...@apache.org wrote: Hi everyone, I would like to start a vote on this CEP, split into three sub-decisions, as discussion has been circular for some time. 1. Do you support adopting this CEP? 2. Do you support the transaction semantics proposed

Re: [VOTE] CEP-16 - Auth Plugin Support for CQLSH

+1 On 10/11/21 4:47 AM, Stefan Miklosovic wrote: Hi list, based on the discussion thread about CEP-16 (1), I would like to have a vote on that. It seems to me CEP-16 is so straightforward there is more or less nothing to discuss in more depth as the feedback it gathered was mostly formal and

Re: [VOTE] Release Apache Cassandra 3.0.25

+1 Kind regards, Michael On 7/25/21 12:40 PM, Brandon Williams wrote: I am proposing the test build of Cassandra 3.0.25 for release. sha1: 06235e93e16d1f483a3b03ba02f8fb29e33305fa Git: https://gitbox.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/3.0.25-tentative Maven

Re: [VOTE] Release Apache Cassandra 3.11.11

+1 Kind regards, Michael On 7/25/21 2:06 PM, Brandon Williams wrote: I am proposing the test build of Cassandra 3.11.11 for release. sha1: 4cafe2288e56e1135d65e76adbcd6c2de9306d6b Git: https://gitbox.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/3.11.11-tentative Maven

Re: [VOTE] Release Apache Cassandra 4.0.0 (third time is the charm)

+1 Kind regards, Michael On 7/22/21 5:40 PM, Brandon Williams wrote: I am proposing the test build of Cassandra 4.0.0 for release. sha1: 902b4d31772eaa84f05ffdc1e4f4b7a66d5b17e6 Git: https://gitbox.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/4.0.0-tentative Maven Artifacts:

Re: Regarding JIRA Cassandra-14227

I updated the severity and complexity of this ticket. It is not a trivial fix, but I agree that as time goes on, this is becoming higher priority to focus some effort on it. (fyi, I'm not volunteering, is way beyond my means :) ) Kind regards, Michael On 6/10/20 11:55 PM, manish khandelwal

Re: [VOTE] Release Apache Cassandra 4.0-alpha4

+1 On 4/10/20 6:02 PM, Mick Semb Wever wrote: Proposing the test build of Cassandra 4.0-alpha4 for release. sha1: d00c004cc10986fc41c2070f9c5d0007e03a45c3 Git: https://gitbox.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/4.0-alpha4-tentative Maven Artifacts:

Re: CircleCI config change?

It has been a few years, but I think we came to basically the same conclusion on build/test skipping in autojobs for CassCI. Most wanted the job runs all the time, but a few wanted to skip runs for scratch or WIP branches, in order to preserve resources when they didn't care what the result

Re: [VOTE] Release dtest-api 0.0.3

updated vote: -1 Thanks for the run through, Mick. On 3/20/20 12:01 PM, Michael Shuler wrote: +1 Code link is actually a branch at: https://github.com/apache/cassandra-in-jvm-dtest-api/tree/CASSANDRA-15539 Just curious why master isn't the active dev branch, since there's nothing

Re: [VOTE] Release dtest-api 0.0.3

+1 Code link is actually a branch at: https://github.com/apache/cassandra-in-jvm-dtest-api/tree/CASSANDRA-15539 Just curious why master isn't the active dev branch, since there's nothing but a license and blank readme there. No biggie, just had to go look for it when I followed the link.

Re: CASSANDRA-15586 4.0 quality testing: Cluster Setup and Maintenance

On 3/18/20 11:15 AM, Ekaterina Dimitrova wrote: Hello everyone, I am interested to help with "CASSANDRA-15586 4.0 quality testing: Cluster Setup and Maintenance" Awesome! There was a short discussion last night on Slack but I know that not everyone keeps an eye on those chats so I decided to

Re: another alpha?

On 3/3/20 12:16 AM, Mick Semb Wever wrote: I'm happy to cut a release later this week or next, once these and others yet to be mentioned get merged. We need to do another round on the release process to wrap up CASSANDRA-14970. Great! I have a little availability over the next week or two,

[RELEASE] Apache Cassandra 3.11.6 released

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

[RELEASE] Apache Cassandra 3.0.20 released

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

[RELEASE] Apache Cassandra 2.2.16 released

The Cassandra team is pleased to announce the release of Apache Cassandra version 2.2.16. 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: [VOTE] Release Apache Cassandra 2.2.16

+1 On 2/10/20 2:31 PM, Mick Semb Wever wrote: Proposing the test build of Cassandra 2.2.16 for release. sha1: c4d9e9ca4ade40b956e37935bce68737b0c063b9 Git: https://gitbox.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/2.2.16-tentative Maven Artifacts:

Re: [VOTE] Release Apache Cassandra 3.0.20

+1 On 2/11/20 2:36 AM, Mick Semb Wever wrote: Proposing the test build of Cassandra 3.0.20 for release. sha1: 89edf5073ba4181dd2f70294cdbcb47f5a45c82e Git: https://gitbox.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/3.0.20-tentative Maven Artifacts:

Re: [VOTE] Release Apache Cassandra 3.11.6

+1 On 2/11/20 2:38 AM, Mick Semb Wever wrote: Proposing the test build of Cassandra 3.11.6 for release. sha1: cb779ab9a631c13a245926f55320392c4468c6f0 Git: https://gitbox.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/3.11.6-tentative Maven Artifacts:

Re: Ideas for Cassandra 2020 - Remote Meetups / Mastermind

This is great, thanks, the project appreciates the effort. 2019 is over, don't worry about the past. Moving forward in little or large steps is the goal. :) If you didn't get a chance to attend the first Contributor Meeting, there will be more. Patrick sent out a survey last week for

Re: Do we need Javadoc in binary distribution? Was: [RELEASE] Apache Cassandra 4.0-alpha3 released

I like this idea for keeping binary deployment size down. I'm not sure how to handle it for the tarballs, but we could certainly split the docs out of the debian and rpm packages to add cassandra-docs_.{deb,rpm} packages, so they are installable separately, if the user wants them. This is

Re: [VOTE] Release Apache Cassandra 4.0-alpha3

On 2/4/20 3:59 PM, Mick Semb Wever wrote: Proposing the test build of Cassandra 4.0-alpha3 for release. sha1: 5f7c88601c65cdf14ee68387ed68203f2603fc29 Git: https://gitbox.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/4.0-alpha3-tentative Maven Artifacts:

Re: [VOTE] Release Apache Cassandra 4.0-alpha3

On 2/3/20 5:21 PM, Mick Semb Wever wrote: Summary of notes: - Artifact set checks out OK with regards to key sigs and checksums. - CASSANDRA-14962 is an issue when not using the current deb build method (using new docker method results in different source artifact creation & use). The docker

Re: Fwd: [CI] What are the troubles projects face with CI and Infra

Only have a moment to respond, but Mick hit the higlights with containerization, parallelization, these help solve cleanup, speed, and cascading failures. Dynamic disposable slaves would be icing on that cake, which may require a dedicated master. One more note on jobs, or more correctly

Re: [VOTE] Release Apache Cassandra 4.0-alpha3

2020 12:27:19 PM CST gpg:using RSA key A4C465FEA0C552561A392A61E91335D77E3E87CB gpg: Can't check signature: No public key Validation FAILED!! # lgtm (I have not `apt-key add`ed key..) mshuler@hana:~/tmp/cassandra-4.0-alpha3$ egrep 'Date:|Changed-By:' *.changes ; grep -A3 Changes: *.changes Dat

Re: [Discuss] num_tokens default in Cassandra 4.0

On 1/31/20 9:58 AM, Dimitar Dimitrov wrote: one corollary of the way the algorithm works (or more precisely might not work) with multiple seeds or simultaneous multi-node bootstraps or decommissions, is that a lot of dtests start failing due to deterministic token conflicts. I wasn't able to fix

Re: [DISCUSS] Switch to using GitHub pull requests?

On 1/23/20 3:53 PM, David Capwell wrote: 2) Nightly build email to dev@? Nope. builds@c.a.o is where these go. https://lists.apache.org/list.html?bui...@cassandra.apache.org Michael - To unsubscribe, e-mail:

Re: [DISCUSS] Switch to using GitHub pull requests?

On 1/23/20 2:13 PM, Mick Semb Wever wrote: ASF policy is that patches from contributors that haven't a ICLA filed can not have their patches automatically run through any ASF CI system. It's up to a committer (or someone who has filed a ICLA) to trigger the test run on the patch. I couldn't

Re: Cassandra CI Status

On 1/11/20 10:02 AM, Mick Semb Wever wrote: This brings up the issue that links to builds on tickets should ideally refer to information that is permanent. This could be done by configuring builds to keep status and logs but not the built artefacts (and/or adding bigger disks). I will now

Re: Cassandra CI Status

On 1/11/20 9:17 AM, Michael Shuler wrote: On 1/11/20 4:48 AM, Mick Semb Wever wrote: This brings up the issue that links to builds on tickets should ideally refer to information that is permanent. This could be done by configuring builds to keep status and logs but not the built

Re: Cassandra CI Status

On 1/11/20 4:48 AM, Mick Semb Wever wrote: This brings up the issue that links to builds on tickets should ideally refer to information that is permanent. This could be done by configuring builds to keep status and logs but not the built artefacts (and/or adding bigger disks). I will now

Re: putting the alphas on the website downloads section

ing that line into risking people running alpha code on accident in a production environment. On Mon, Nov 4, 2019 at 3:10 PM Michael Shuler wrote: I will also add that I did send the user@ list 4.0-alpha release notes, along with dev@, and also added to the @cassandra tweet last week. I thought th

Re: putting the alphas on the website downloads section

:06 PM, Michael Shuler wrote: -1 (I looked into this when we released 4.0-alpha1) "During the process of developing software and preparing a release, various packages are made available to the developer community for testing purposes. Do not include any links on the project website that

Re: putting the alphas on the website downloads section

-1 (I looked into this when we released 4.0-alpha1) "During the process of developing software and preparing a release, various packages are made available to the developer community for testing purposes. Do not include any links on the project website that might encourage non-developers to

Re: [VOTE] Cassandra Enhancement Proposal (CEP) documentation

+1 Scott, was your NGCC talk videoed and uploaded anywhere? I would love to watch, since I missed the event. Kind regards, Michael On 11/1/19 9:07 AM, Scott Andreas wrote: +1 nb On Nov 1, 2019, at 5:36 AM, Benedict Elliott Smith wrote: +1 On 01/11/2019, 12:33, "Mick Semb Wever"

Re: moving the site from SVN to git

issing something obvious? Jon On Tue, Oct 29, 2019 at 1:28 PM Jon Haddad wrote: I'll take a look at the website generation. Thanks for fixing manually for now. On Tue, Oct 29, 2019 at 1:16 PM Michael Shuler wrote: I have updated the new releases in: src/_data/releases.yaml I ran t

[RELEASE] Apache Cassandra 4.0-alpha2 released

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

[RELEASE] Apache Cassandra 2.2.15 released

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

[RELEASE] Apache Cassandra 3.11.5 released

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

[RELEASE] Apache Cassandra 3.0.19 released

The Cassandra team is pleased to announce the release of Apache Cassandra version 3.0.19. 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 can take care of it tomorrow. Reference: https://cwiki.apache.org/confluence/display/INFRA/.asf.yaml+features+for+git+repositories#id-.asf.yamlfeaturesforgitrepositories-Publishingabranchtoyourprojectwebsite On Thu, Oct 3, 2019 at 10:57 AM Michael Shuler wrote: committed! :) https

Re: [VOTE PASSED] Release Apache Cassandra 4.0-alpha2

This vote passed with 6 binding +1, 3 non-binding +1, and no other votes. Kind regards, Michael Shuler On 10/24/19 12:26 PM, Michael Shuler wrote: I propose the following artifacts for release as 4.0-alpha2. sha1: ca928a49c68186bdcd57dea8b10c30991c6a3c55 Git: https://gitbox.apache.org/repos

Re: [VOTE PASSED] Release Apache Cassandra 3.11.5

This vote passed with 7 binding +1, 2 non-binding +1, and no other votes. Kind regards, Michael Shuler On 10/24/19 12:26 PM, Michael Shuler wrote: I propose the following artifacts for release as 3.11.5. sha1: b697af87f8e1b20d22948390d516dba1fbb9eee7 Git: https://gitbox.apache.org/repos/asf

Re: [VOTE PASSED] Release Apache Cassandra 3.0.19

This vote passed with 8 binding +1, 3 non-binding +1, and no other votes. Kind regards, Michael Shuler On 10/24/19 12:25 PM, Michael Shuler wrote: I propose the following artifacts for release as 3.0.19. sha1: a81bfd6b7db3a373430b3c4e8f4e930b199796f0 Git: https://gitbox.apache.org/repos/asf

Re: [VOTE PASSED] Release Apache Cassandra 2.2.15

This vote passed with 8 binding +1, 2 non-binding +1, and no other votes. Kind regards, Michael Shuler On 10/24/19 12:25 PM, Michael Shuler wrote: I propose the following artifacts for release as 2.2.15. sha1: 4ee4ceea28a1cb77b283c7ce0135340ddff02086 Git: https://gitbox.apache.org/repos/asf

[VOTE] Release Apache Cassandra 3.0.19

I propose the following artifacts for release as 3.0.19. sha1: a81bfd6b7db3a373430b3c4e8f4e930b199796f0 Git: https://gitbox.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/3.0.19-tentative Artifacts:

[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:

[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:

[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:

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

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

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

Re: Can we kick off a release?

d 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: 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

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 periodic

Re: moving the site from SVN to git

. 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 svn checkout of the above

Re: moving the site from SVN to git

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, 2019 at 6:04 AM Michael Shuler

[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

[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

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

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-alpha1

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: 4.0 alpha before apachecon?

ANDRA%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 a few days of availabili

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,

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

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

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

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!

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: 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

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

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

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

"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.

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

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

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: Cassandra repo keys are revoked

ed > 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 E19

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

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

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

[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

[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

[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

  1   2   3   4   >