Re: [VOTE] Release Apache Cassandra 4.0.2

(This was a +1 on the release, to be clear, not a +1 on the sentiment below, which I appreciate but still believe we should proceed with the release) On Tue, Feb 8, 2022 at 3:44 PM Jeff Jirsa wrote: > +1 > > > On Tue, Feb 8, 2022 at 3:37 PM Joshua McKenzie > wrote: > >> I find myself agreeing

Re: [VOTE] Release Apache Cassandra 4.0.2

+1 On Tue, Feb 8, 2022 at 3:37 PM Joshua McKenzie wrote: > I find myself agreeing with Jeremiah's sentiment here. > > For example, we're asking people that are on 4.0.1 to make the difficult > choice between accepting the risk of whatever prompts an urgent release vs. > accepting the risk of

Re: [VOTE] Release Apache Cassandra 4.0.2

I find myself agreeing with Jeremiah's sentiment here. For example, we're asking people that are on 4.0.1 to make the difficult choice between accepting the risk of whatever prompts an urgent release vs. accepting the risk of potentially destabilizing their GA critical infrastructure. The 4.0

Re: [DISCUSS] CEP-7 Storage Attached Index

Regarding SASI deprecation and removal, I think I'm on the same page as Henrik. The grand glorious future involves getting to feature parity with and then completely replacing legacy 2i and SASI, but the CEP need not specify a hard timeline for this. With respect to OR support, I'm actually

Re: [DISCUSS] Non Coding Committers

+1 to this conversation, from a Docs wonk. :-) On Tue, Feb 8, 2022 at 1:40 PM Patrick McFadin wrote: > Sharan has done a good job shining a spotlight on something that has > created a weird bottleneck in the project. Docs and the Cassandra website > are all in-tree, but it takes somebody who

Re: [DISCUSS] Non Coding Committers

Sharan has done a good job shining a spotlight on something that has created a weird bottleneck in the project. Docs and the Cassandra website are all in-tree, but it takes somebody who probably isn't even working on those things to commit any changes. Dinesh nailed it. It's silly. I'm sure the

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

My quick reading of the code suggests that schema will override the operator's default preference in the YAML. In the event of a bug in the new implementation, there could be situation where the operator might need to override this via the YAML. > On Feb 8, 2022, at 12:29 PM, Jeremiah D Jordan

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

I don’t really see most users touching the default implementation. I would expect the main reason someone would change would be 1. They run into some bug that is only in one of the implementations. 2. They have persistent memory and so want to use

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

FWIW, I think the proposed approach to configuration is fine. I think selecting a choice for the user should be done simply and deterministically. We should probably default to Trie based memtables for users with a fresh config file, and we can consider changing the default in a later release

Re: [VOTE] Release Apache Cassandra 3.11.12

-1 nb for same reason as I said for the 4.0.2 vote here: https://lists.apache.org/thread/7zc22z5vw5b58hdzpx2nypwfzjzo3qbr > On Feb 8, 2022, at 4:10 AM, Dorian ROSSE wrote: > > Hello Scott, > > > Yours links should work but

Re: [VOTE] Release Apache Cassandra 3.0.26

-1 nb for same reason as I said for the 4.0.2 vote here: https://lists.apache.org/thread/7zc22z5vw5b58hdzpx2nypwfzjzo3qbr > On Feb 8, 2022, at 6:15 AM, Mick

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

Thank you for sharing the perf test results. Going back to the schema vs yaml configuration. I am concerned users may pick the wrong implementation for their use-case. Is there any chance for us to automatically pick a MemTable implementation based on heuristics? Do we foresee users ever

Re: [VOTE] Release Apache Cassandra 4.0.2

-1 nb So we just voted on an approved the CI process page recently: https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=199530280 Where we said: "All releases by default are expected to have a green test

Re: [VOTE] release cassandra-harry 0.0.1

+1

Re: [VOTE] release cassandra-harry 0.0.1

+1 On Mon, Feb 7, 2022 at 8:44 AM Alex Petrov wrote: > Proposing the test build of cassandra-harry 0.0.1 for release, to start > using it in Cassandra tree. > > Repository: > > https://gitbox.apache.org/repos/asf?p=cassandra-harry.git;a=shortlog;h=refs/tags/0.0.1 > > Candidate SHA: > >

Re: [VOTE] release cassandra-harry 0.0.1

+1nb > On Feb 8, 2022, at 4:18 AM, Brandon Williams wrote: > > +1 > >> On Mon, Feb 7, 2022 at 8:44 AM Alex Petrov wrote: >> >> Proposing the test build of cassandra-harry 0.0.1 for release, to start >> using it in Cassandra tree. >> >> Repository: >>

Re: [VOTE] release cassandra-harry 0.0.1

+1 On Mon, Feb 7, 2022 at 8:44 AM Alex Petrov wrote: > > Proposing the test build of cassandra-harry 0.0.1 for release, to start using > it in Cassandra tree. > > Repository: > https://gitbox.apache.org/repos/asf?p=cassandra-harry.git;a=shortlog;h=refs/tags/0.0.1 > > Candidate SHA: >

Re: [VOTE] Release Apache Cassandra 4.0.2

+1 Checked - signing correct - checksums are correct - source artefact builds - binary artefact runs - debian package runs - redhat package runs ( used https://github.com/apache/cassandra-builds/pull/32 ) On Tue, 8 Feb 2022 at 11:12, Marcus Eriksson wrote: > +1 > > On Mon, Feb 07, 2022 at

Re: [VOTE] Release Apache Cassandra 3.11.12

+1 Checked - signing correct - checksums are correct - source artefact builds - binary artefact runs - debian package runs - redhat package runs ( used https://github.com/apache/cassandra-builds/pull/32 ) On Tue, 8 Feb 2022 at 11:13, Marcus Eriksson wrote: > +1 > > On Mon, Feb 07, 2022 at

Re: [VOTE] Release Apache Cassandra 3.0.26

+1 Checked - signing correct - checksums are correct - source artefact builds - binary artefact runs - debian package runs - redhat package runs ( used https://github.com/apache/cassandra-builds/pull/32 ) On Tue, 8 Feb 2022 at 11:12, Marcus Eriksson wrote: > +1 > > On Mon, Feb 07, 2022 at

Re: [VOTE] Release Apache Cassandra 4.0.2

+1. Smoke tested debs and rpms, unit tests passed. On Mon, Feb 7, 2022 at 8:15 AM Mick Semb Wever wrote: > > Proposing the test build of Cassandra 4.0.2 for release. > > sha1: 25012d2fec1984cc9c1a352f214eb912ca4f10f5 > > Git: >

Re: [VOTE] Release Apache Cassandra 3.11.12

+1 On Mon, Feb 07, 2022 at 03:14:25PM +0100, Mick Semb Wever wrote: > Proposing the test build of Cassandra 3.11.12 for release. > > sha1: b44ff92eb2921e8d66fe2e994cb27289d3786faa > > Git: > https://gitbox.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/3.11.12-tentative > > Maven

Re: [VOTE] Release Apache Cassandra 4.0.2

+1 On Mon, Feb 07, 2022 at 03:14:36PM +0100, Mick Semb Wever wrote: > Proposing the test build of Cassandra 4.0.2 for release. > > sha1: 25012d2fec1984cc9c1a352f214eb912ca4f10f5 > > Git: > https://gitbox.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/4.0.2-tentative > > Maven

Re: [VOTE] Release Apache Cassandra 3.0.26

+1 On Mon, Feb 07, 2022 at 03:14:15PM +0100, Mick Semb Wever wrote: > Proposing the test build of Cassandra 3.0.26 for release. > > sha1: b18adcba1a808cf77576905dc2ceccd7783bdb18 > > Git: > https://gitbox.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/3.0.26-tentative > > Maven