netty version in binary cassandra-java-driver 3.6

x27;t include the NettyRuntime class. Did I downloaded the wrong tarball of the java driver? Or is the netty version in this tarball also too old? Thanks for helping, Michael - To unsubscribe, e-mail: dev-uns

Re: Should we change 4.1 to G1 and offheap_objects ?

update the commented out G1 settings in 4.1.1 to match those becoming the default in trunk. +1 to G1 default in trunk and a recommendation in 4.1.1 NEWS.txt. I agree with Aleksey and others, trunk is the right place to change defaults. Kind regards, Michael

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 <https://incubator.apache.

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

. Sounds like a good contribution :) Kind regards, Michael On 1/15/24 03:22, Alexander Shusherov wrote: Hello Cassandra Developers! Recently we explored the behavior of logback in Cassandra 4.1 (there was a hypothesis about a bug in SizeAndTimeBasedRollingPolicy, however it was not confirmed).

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

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 <https://cwiki.apache.

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 <https://incubator.apache.org/ip-clearance/cassandra-gocql-driver.html>

Re: Hi-Rez of Apache Cassandra logo??

Apache Cassandra logos provided by Scott Andreas Since Scott uploaded them to a temporary location, let's add them here. https://lists.apache.org/thread.html/981adf13e8d483d9de41bf5ab30328aafe8544da6b36036e64744046@%3Cdev.cassandra.apache.org%3E -- Kind regards, Michael On 05/18/2018 12:23 AM,

Re: Planning to port cqlsh to Python 3 (CASSANDRA-10190)

Hi, Should definitely be cross compatible with Python 2/3. Most of the systems (such as those running on RHEL7 or distros based on it like CentOS) are shipping with 2.7 only by default. And these systems are probably going to be used for a long time to run Cassandra. IIRC, there's no major d

Re: Planning to port cqlsh to Python 3 (CASSANDRA-10190)

2018/06/01 07:40:04, Michael Burman wrote: IIRC, there's no major distribution yet that defaults to Python 3 (I think Ubuntu & Debian are still defaulting to Python 2 also). This will happen eventually (maybe), but not yet. Discarding Python 2 support would mean more base-OS work for most

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

Re: Small improvement on website

assandra's..." Thanks! Fixed. If necessary, I am able to create a JIRA for this ;) Nah :) -- Kind regards, Michael - To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org For additional commands, e-mail: dev-h...@cassandra.apache.org

[VOTE] Release Apache Cassandra 2.2.13

) http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=blob_plain;f=CHANGES.txt;hb=refs/tags/2.2.13-tentative [2]: (NEWS.txt) http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=blob_plain;f=NEWS.txt;hb=refs/tags/2.2.13-tentative -- Michael

[VOTE] Release Apache Cassandra 3.0.17

) http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=blob_plain;f=CHANGES.txt;hb=refs/tags/3.0.17-tentative [2]: (NEWS.txt) http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=blob_plain;f=NEWS.txt;hb=refs/tags/3.0.17-tentative -- Michael

[VOTE] Release Apache Cassandra 3.11.3

) http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=blob_plain;f=CHANGES.txt;hb=refs/tags/3.11.3-tentative [2]: (NEWS.txt) http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=blob_plain;f=NEWS.txt;hb=refs/tags/3.11.3-tentative -- Michael

[VOTE FAILED] Release Apache Cassandra 3.11.3

Based on the CASSANDRA-14555 notes and revert of the CASSANDRA-14252 from the cassandra-3.0/3.11 branches, I'm also a -1 for release. Kind regards, Michael On 07/03/2018 02:14 AM, Sam Tunnicliffe wrote: > -1 I think CASSANDRA-14252 should be reverted from 3.0 & 3.11, at least the

[VOTE FAILED] Release Apache Cassandra 3.0.17

Based on the CASSANDRA-14555 notes and revert of the CASSANDRA-14252 from the cassandra-3.0/3.11 branches, I'm also a -1 for release. Kind regards, Michael On 07/03/2018 02:14 AM, Sam Tunnicliffe wrote: > -1 I think CASSANDRA-14252 should be reverted from 3.0 & 3.11, at least the

[VOTE FAILED - VETO] Release Apache Cassandra 2.2.13

this release. Kind regards, Michael On 07/04/2018 06:18 AM, kurt greaves wrote: > Actually taking back my +1, seems like we've got a fair amount of dtests > (at least 7) failing consistently on 2.2, and another one that's very flaky. > Last completed runs are here: > https:/

Re: Scratch an itch

On 07/12/2018 07:38 PM, Stefan Podkowinski wrote: this point? Also, if we tell someone that their contribution will be reviewed and committed later after 4.0-beta, how is that actually making a difference for that person, compared to committing it now for a 4.x version. It may be satisfying to ge

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

Re: reroll the builds?

he tests on 2.2, 3.0, 3.11 branches and link them? Thanks! Michael - To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org For additional commands, e-mail: dev-h...@cassandra.apache.org

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

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

Re: [Discuss] Accept GoCQL driver donation

elease, etc. mechanics more flexibly. I see little to no advantage to including allthethings in-tree. If there comes a time that particular contrib items do make sense to include in the main repository, dropping them in would be no problem. -- Michael > On Fri, Aug 31, 2018 at 7:14 AM Nate

Re: [Discuss] Accept GoCQL driver donation

upport of a committer who focused purely on documentation and website content, for instance. It's a matter of trusting a contributor to know what and where to commit, as well as where/what/when not to. -- Kind regards, Michael

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, CA

Re: Moving tickets out of 4.0 post freeze

uppose this also means all the tickets for 4.x should be updated to 4.0.x, 4.0 to 4.0.0, etc. -- Michael - To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org For additional commands, e-mail: dev-h...@cassandra.apache.org

Re: Moving tickets out of 4.0 post freeze

an create another thread, but since versions break tests and drivers and such, and were all about making sure tests are clean, it's relevant, along with deciding what version to move new feature tickets out to. Michael >> On 24 Sep 2018, at 17:55, Jeremiah D Jordan >> wrote: >

Re: Implicit Casts for Arithmetic Operators

Hi, I'm not sure if I would prefer the Postgres way of doing things, which is returning just about any type depending on the order of operators. Considering it actually mentions in the docs that using numeric/decimal is slow and also multiple times that floating points are inexact. So doing some m

Re: CASSANDRA-13241 lower default chunk_length_in_kb

t's > stable, time to start testing"? Creating a cassandra-4.0 branch would allow trunk to, for instance, get a default config value change commit and get more testing. We might forget again, from what I understand of

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

hyperic/sigar/issues/77 https://comm.support.ca.com/kb/devtest-9x-server-component-fails-to-start-error-sigaramd64winntdll0x14ed4/kb41311 Michael - To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org For additional commands, e-mail: dev-h...@cassandra.apache.org

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

On 11/12/18 5:37 PM, Michael Shuler wrote: Issue with upstream links to: https://github.com/hyperic/sigar/issues/77 .. clip. Considering the Sigar has been unmaintained for years (and has large amount of unfixed bugs), should we consider removing it from the project? It's not used muc

Re: Implicit Casts for Arithmetic Operators

;>>>> being raised. The rules for arithmetic are generally governed > by > >>>>> Subclause 6.12, "". > >>>>> " > >>>>> > >>>>> Section 6.12 numeric value expressions: > >>>>>

Re: RES: Implicit Casts for Arithmetic Operators

age to the list. You will still have to follow the approval link you'll get from the list moderation removal CC here, sent on your behalf... -- Kind regards, Michael - To unsubscribe, e-mail: dev-unsubscr...@cassandra.apa

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 > <https://cwiki.apache.org/confluence/display/CASSANDRA/JIRA+Workflow+Proposals>* > to the Jira Workflow for the project. The vote will be open for 72 hours**. > > I am, of co

Re: Git Repo Migration

longer we wait, the more things people have in flight and they get bothered about being interrupted. Just interrupt ASAP, IMO. Michael On 1/4/19 4:49 AM, Sam Tunnicliffe wrote: > As per the announcement on 7th December 2018[1], ASF infra are > planning to shutdown the service behind git-

Re: Git Repo Migration

. - https://builds.apache.org/job/Cassandra-Job-DSL/ The only other consideration I can think of after migration is checking the git.a.o bare and github mirror post-commit hooks work as expected. - http://git.apache.org/cassandra.git/ Michael On 1/4/19 2:00 PM, Jonathan Haddad wrote: > Silence can

Re: Who should be in our distribution KEYS file?

es release frequency. Did someone request a release to be made or are we on some assumed date interval? Michael On 1/7/19 2:30 PM, Jonathan Haddad wrote: > That's a good point. Looking at the ASF docs I had assumed the release > manager was per-project, but on closer inspection it appear

Re: Who should be in our distribution KEYS file?

cket on release artifacts. There are also some comments in the details of http://cassandra.apache.org/doc/latest/development/release_process.html that could be streamlined and include fixing the steps, temporary upload problems, etc. Work on temporary uploads for staging the artifacts could be useful for #

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?

ate GPG keys every release, that's not nice to our users. If there is a way to get the repos set up correctly in bintray, and it's OK with INFRA to use the bintray key signing feature, great. We should set up a new package signing key and configure bintray to sign the metadata. One change for a

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/apa

EOL 2.1 series?

st call it EOL an do one last release of the few fixes that did get committed. Comments? Michael - To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org For additional commands, e-mail: dev-h...@cassandra.apache.org

Re: Who should be in our distribution KEYS file?

page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16738342 tl;dr: - I think we can use the bintray key to sign the repos, there's precedent - using bintray to build the deb/rpm repos, all version in each suite (22x, 30x, ..) will be installable, instead of just the latest version Michael On 1/9/19 8:06 AM, Stefan Po

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

#x27;t have a massive amount of time to troubleshoot more. I did commit the release target fix. -- Michael - To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org For additional commands, e-mail: dev-h...@cassandra.apache.org

[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

users we are doing something, if we aren't and haven't been. Michael On 2/3/19 5:24 PM, Anthony Grasso wrote: > +1 non-binding, for the release of 2.1.21 > > Regarding EOL of 2.1.x, did we announce in the past that 2.1.21 would be > the final release? > > According to the

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

I count 7 binding +1's, 1 non-binding +1 vote, and no others, so this vote passes. I'll publish the artifacts as soon as I can. Thanks for the discussion on support life of the 2.1 branch. I will not be making any changes to the notes on the download page. Kind regards, Michael On 2

[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

see any conf/cassandra.yaml comment in the diff for the valid class_name configuration option to use. Seems interesting, and there are comments about 4.0 being in a freeze and all, but OK on it being non-default. -- Michael On 2/15/19 11:43 AM, Ariel Weisberg wrote: > Hi, > > I am

Re: Looking for common cases in cassandra fit to autoheal

wish to drop the unenforceable email footer or use a personal email address, if it's appended by your mail server. -- Kind regards, Michael http://www.pbandjelly.org/2011/03/to-whom-it-may-concern/ On 3/1/19 2:33 PM, Sundaramoorthy, Natarajan wrote: > Can someone please reply

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

mshuler mshuler 50385890 Mar 6 21:16 apache-cassandra-4.0-SNAPSHOT-bin.tar.gz -rw-r--r-- 1 mshuler mshuler 46198947 Mar 6 21:16 apache-cassandra-4.0-SNAPSHOT-src.tar.gz Or you could drop a dual-JDK install on your machine, export the env vars you found and `ant artifa

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

or the lowest common denominator in real world usage, not the latest release from upstream. Super strong opinion, here. -- Michael - To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org For additional commands, e-mail: dev-h...@cassandra.apache.org

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

diting the download page? Have some other goal timeframe in mind? -- Warm regards, Michael - To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org For additional commands, e-mail: dev-h...@cassandra.apache.org

Re: Time for a new 3.0/3.11 release?

pop up. -- Kind regards, Michael - To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org For additional commands, e-mail: dev-h...@cassandra.apache.org

Re: Time for a new 3.0/3.11 release?

and some subjective observation of that specific jira. (An update on the current state of in-progress/review statuses for 4.0 jiras from the folks working on them would be awesome! hint hint.) Kind regards, Michael On Wed, Jul 3, 2019, 1:28 AM Mick Semb Wever mailto:m...@apache.org>>

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: Isn't there a workable cassandra java source for developing as other big data system?

tml build steps pasted in slack:#cassandra: cd /tmp/ git clone https://github.com/apache/cassandra.git cd cassandra/ git checkout cassandra-3.11.3 ant artifacts BUILD SUCCESSFUL Total time: 1 minute 32 seconds -- Kind regards, Michael On 7/16/19 9:01 AM, Benedict Elliott Smith wrote: 3.11.

Re: Apache Cassandra Virtual meetings

ll be offshore with no internet access for several days, but just want a way to keep up with conversations and presentations. -- Warm regards, Michael - To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org For addit

Re: Contributing cassandra-diff

ility! Michael On 8/22/19 10:33 AM, Sankalp Kohli wrote: A different repo will be better On Aug 22, 2019, at 6:16 AM, Per Otterström wrote: Very powerful tool indeed, thanks for sharing! I believe it is best to keep tools like this in different repos since different tools will probably have diff

Re: Stability of MaterializedView in 3.11.x | 4.0

/19b7fcfd3b47f1526d6e993b3bb97f6c43e5ce204bc976ec0701cdd3@ Quick JQL for open tickets with "mv": https://issues.apache.org/jira/issues/?jql=project%20%3D%20CASSANDRA%20AND%20text%20~%20mv%20AND%20status%20!%3D%20Resolved -- Michael On 8/27/19 5:01 AM, pankaj gajjar wrote: Hello, concern about Ma

Re: 4.0 alpha before apachecon?

and have a little network access in the middle of that time, but I'm not counting on it. -- Michael On 8/28/19 10:51 AM, Jon Haddad wrote: Hey folks, I think it's time we cut a 4.0 alpha release. Before I put up a vote thread, is there a reason not to have a 4.0 alpha before ApacheCo

Re: Builds email notifications

ml 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. -- Kind regards, Michael -

Re: Builds email notifications

are usually pretty clear where the issue might be. Just do it in prod, once it looks about what we want. ;) -- Michael - To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org For additional commands, e-mail: dev-h...@cassandra.apache.org

Re: 4.0 alpha before apachecon?

apachecassandra-1174/org/apache/cassandra/apache-cassandra/4.0-alpha1/ Michael On 8/29/19 2:30 PM, Joseph Lynch wrote: We hashed this out a bit in slack and I think the current rough consensus (please speak up if you don't agree) is that we update our release guidelines [1] to allow API chang

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

Thanks a bunch for the test runs. Most of those upgrade tests show "RuntimeError: You need to set JAVA8_HOME," so it does look like a systemic, generic issue to resolve there somewhere in dtest. Thanks again! Michael On 9/5/19 8:08 PM, Joseph Lynch wrote: Following

[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

Re: moving the site from SVN to git

or all projects? I'll let this roll for a while I run an errand and report back! Michael On 10/2/19 9:30 PM, Jon Haddad wrote: Daniel referred me to the GitBox self service system. I've attempted to port the site over using the tool Michael suggested, but after a couple hours

Re: moving the site from SVN to git

a local path as the source to try to speed things up, after I got my first few timeouts, but that fails. Curious if anyone really cares if we lose a few early commits - if so, I can try to figure out the old path and start again. Michael On 10/3/19 11:14 AM, Jon Haddad wrote: Thanks for ta

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

  1   2   3   4   5   6   7   >