Re: [VOTE] Release Apache Cassandra 3.11.12

+1 > On Feb 8, 2022, at 12:22 PM, Jeremiah D Jordan > wrote: > > -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

Re: [VOTE] Release Apache Cassandra 3.0.26

+1 > On Feb 8, 2022, at 12:22 PM, Jeremiah D Jordan > wrote: > > -1 nb for same reason as I said for the 4.0.2 vote here: > https://lists.apache.org/thread/7zc22z5vw5b58hdzpx2nypwfzjzo3qbr > >

Re: [VOTE] Release Apache Cassandra 4.0.2

+1 on the release > On Feb 8, 2022, at 3:44 PM, Jeff Jirsa wrote: > > (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

Re: [DISCUSS] CEP-7 Storage Attached Index

> Is there some mechanism such as experimental flags, which would allow the > SAI-only OR support to be merged into trunk FWIW, I’m OK with this merging to trunk, either hidden behind a CI-only flag or exposed to the user via some experimental flag (and a suitable NEWS.txt). We’ve discussed the

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

TBH, I don't have an opinion on the configuration. I just want to say that if at the end we decide the configuration in the YAML should override the table schema, I would like to recommend that we specifying a list of whitelisted (or blacklisted) "templates" in the YAML file, and the template c

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

Why not have some default templates that can be specified by the schema without touching the yaml, but overridden in the yaml as necessary? From: Branimir Lambov Date: Wednesday, 9 February 2022 at 09:35 To: dev@cassandra.apache.org Subject: Re: [DISCUSS] CEP-19: Trie memtable implementation If

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

If I understand this correctly, you prefer _not_ to have an option to give the configuration explicitly in the schema. I.e. force the configurations ("templates" in current terms) to be specified in the yaml, and only allow tables to specify which one to use among them? This does sound at least as

Re: [DISCUSS] Non Coding Committers

Thanks a lot Sharan, Patrick and Lorina. It is a perfectly valid point that the PMC members have recognized for some time already and are actively working on. 😊 Le mar. 8 févr. 2022 à 23:07, Lorina Poland a écrit : > +1 to this conversation, from a Docs wonk. :-) > > On Tue, Feb 8, 2022 at 1:40