Re: Capabilities

Firstly, glad to see the support and enthusiasm here and in the recent Slack discussion. I think there is enough for me to start drafting a CEP. Stefan, global configuration and capabilities do have some overlap but not full overlap. For example, you may want to set globally that a cluster enables

Re: Capabilities

Hi Jordan, what would this look like from the implementation perspective? I was experimenting with transactional guardrails where an operator would control the content of a virtual table which would be backed by TCM so whatever guardrail we would change, this would be automatically and transparent

Re: Capabilities

+1 and happy to help as well on this effort On 2024/12/19 20:21:08 Doug Rohrer wrote: > +1 (nb) and will be happy to help, especially providing input from the > Analytics side. > > Thanks Jordan! > > > On Dec 19, 2024, at 12:00 PM, Paulo Motta wrote: > > > > Nice stuff! I support this proposa

Re: Capabilities

+1 (nb) and will be happy to help, especially providing input from the Analytics side. Thanks Jordan! > On Dec 19, 2024, at 12:00 PM, Paulo Motta wrote: > > Nice stuff! I support this proposal and would be happy to help on this. > > On Wed, Dec 18, 2024 at 6:00 PM Jordan West

Re: Capabilities

Nice stuff! I support this proposal and would be happy to help on this. On Wed, Dec 18, 2024 at 6:00 PM Jordan West wrote: > In a recent discussion on the pains of upgrading one topic that came up is > a feature that Riak had called Capabilities [1]. A major pain with upgrades > is that each nod

Re: Capabilities

+1 (nb) to improving the upgrade experience for Cassandra including opting into features and making rollbacks easier. At a higher level, I know of multiple users of Cassandra with large clusters that have run into these awkward situations where you're half upgraded and there are a variety of

Re: Capabilities

Love it. Big +1 On Thu, Dec 19, 2024 at 8:41 AM Bernardo Botella < conta...@bernardobotella.com> wrote: > +1 to the positive sentiment of such a feature. Huge benefit towards > reducing risks. > > > On Dec 19, 2024, at 8:31 AM, Patrick McFadin wrote: > > > > Thanks for bringing this back, Jord

Re: Capabilities

+1 to the positive sentiment of such a feature. Huge benefit towards reducing risks. > On Dec 19, 2024, at 8:31 AM, Patrick McFadin wrote: > > Thanks for bringing this back, Jordan. I had completely forgotten > about Riak's Capabilities support. That was a fan favorite for > operators, along wi

Re: Capabilities

Thanks for bringing this back, Jordan. I had completely forgotten about Riak's Capabilities support. That was a fan favorite for operators, along with a couple other interesting ways to control the upgrade process. +1 on a CEP from me. On Thu, Dec 19, 2024 at 7:38 AM Josh McKenzie wrote: > > Str

Re: Capabilities

Strong +1. Much like having repair scheduling built in to the ecosystem, this feels like table stakes for having a self-contained, usable distributed database. On Wed, Dec 18, 2024, at 6:11 PM, Dinesh Joshi wrote: > Hi Jordan, > > Thank you for starting this thread. This is a great idea. From a

Re: Cassandra 5 Upgrade - Storage Compatibility Modes

Hi Brandon, I am not sure which part changes after CASSANDRA-20118, there is still the system mismatch going to CASSANDRA_4 caused by the change in system.compaction_history, and going to UPGRADING, this is caused by the 2 different sstable formats, so nothing that CASSANDRA-20118 fixes. So w

Re: Cassandra 5 Upgrade - Storage Compatibility Modes

On Thu, Dec 19, 2024 at 4:11 AM Paul Chandler wrote: > C*4 -> CASSANDRA_4 : There is a schema mismatch, and hints are not sent from > C*4 node to C*5 nodes. > CASSANDRA_4 -> UPGRADING: Repairs are not possible and Nodes cannot be added > or replaced. > UPGRADING-> NONE: No issues. I'll note thi

Cassandra 5 Upgrade - Storage Compatibility Modes

All, As suggested by Scott Andreas I am bringing this discussion to the dev mailing list. A couple of days ago I posted a question on the user mailing list [1] about the storage compatibility modes and whether you can go straight to SCM (NONE) from Cassandra 4. I am currently do some presenta