FixVersion house cleaning

With the dropping of .MINOR in semver simplifying some things in our release we have some FixVersion updating to consider. For those that might not know - we use the ".X" FixVersion to indicate something is intended for a specific release line, then resolve the "X" to the number of the release

Re: FixVersion house cleaning

. On Sat, 17 May 2025 at 14:57, Josh McKenzie wrote: > With the dropping of .MINOR in semver simplifying some things in our > release we have some FixVersion updating to consider. > > For those that might not know - we use the ".X" FixVersion to indicate > something is intended for a specif

Re: One Board to Rule Them All (or: ecosystem JIRA's are now integrated in our kanban board)

. On Fri, 16 May 2025 at 20:53, Josh McKenzie wrote: > https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=484 > Nice, thank you Josh. It looks like the swimline for "Patch 5.0.x" is missing.

Re: Welcome Bret McGuire as Cassandra PMC Member!

Congratulations!JaydeepOn May 16, 2025, at 6:47 PM, guo Maxwell wrote:Congrats!!Jon Haddad 于2025年5月17日周六 08:10写道：Congrats!!On Fri, May 16, 2025 at 4:13 PM Alexandre DUTRA wrote:Great news, and so well deserved! Congratulations Bret!Le ven. 16 mai 202

Re: Stricter repair time requirements necessary to prevent data resurrection than advised by docs

Jeremiah, you’re right, I’ve been using “repair” to mean a cluster-level repair as opposed to a single “nodetool repair” operation, and the Cassandra docs mean “nodetool repair” when referring to a repair. Thanks for pointing that out! I agree that the recommendation to run a “nodetool repair” on e

Re: Stricter repair time requirements necessary to prevent data resurrection than advised by docs

>Repairs managed by Reaper and Scylla Manager do not guarantee a deterministic ordering or timing of individual nodetool repair operations they manage between separate cycles, breaking the "you are performing the cycles in the same order around the nodes every time” assumption. That’s the context f

Re: [DISCUSS] CEP-48: First-Class Materialized View Support

Yeah, this is exactly what i suggested in a different part of the thread. The transformative repair could be done against the local index, and the local index can repair against the global index. It opens up a lot of possibilities, query wise, as well. On Sat, May 17, 2025 at 1:47 PM Blake Eggle

Re: [DISCUSS] CEP-48: First-Class Materialized View Support

What if you built the merkle tree for each sstable as a storage attached index? Then your repair is merging merkle tables. On Sat, May 17, 2025 at 4:57 PM Runtian Liu wrote: > > I think you could exploit this to improve your MV repair design. Instead > of taking global snapshots and persisting

Re: [DISCUSS] CEP-48: First-Class Materialized View Support

Could we could do that for regular repair as well? which would make a validation possible with barely any IO? Sstable attached merkle trees? On Sat, May 17, 2025 at 5:36 PM Jon Haddad wrote: > What if you built the merkle tree for each sstable as a storage attached > index? > > Then your rep

Re: [DISCUSS] CEP-48: First-Class Materialized View Support

For each row, when calculating its hash, we first need to merge all the SSTables that contain that row. We cannot attach a Merkle tree directly to each SSTable, because merged Merkle trees would produce different hash values for the same data if the compaction states differ. On Sat, May 17, 2025 a

Re: [DISCUSS] CEP-48: First-Class Materialized View Support

> I think you could exploit this to improve your MV repair design. Instead of taking global snapshots and persisting merkle trees, you could implement a set of secondary indexes on the base and view tables that you could quickly compare the contents of for repair. We actually considered this appro

Re: Welcome Bret McGuire as Cassandra PMC Member!

Welcome Bret and congratulations! On Sat, May 17, 2025 at 10:46 AM Jaydeep Chovatia < chovatia.jayd...@gmail.com> wrote: > Congratulations! > > Jaydeep > > On May 16, 2025, at 6:47 PM, guo Maxwell wrote: > >  > Congrats!! > > Jon Haddad 于2025年5月17日周六 08:10写道： > >> Congrats!! >> >> >> On Fri, M