Re: [DISCUSS] Future of MVs

2020-07-01 Thread Benjamin Lerer
> > "Make the scan faster" > "Make the scan incremental and automatic" > "Make it not blow up your page cache" > "Make losing your base replicas less likely". > > There's a concrete, real opportunity with MVs to create integrity > assertions we're missing. A dangling record from an MV that would po

Re: [DISCUSS] Future of MVs

2020-07-01 Thread Jasonstack Zhao Yang
> I agree with Jeff that there is some stuff to do to address the current MV > issues and I am willing to focus on making them production ready. +1 On Wed, 1 Jul 2020 at 15:42, Benjamin Lerer wrote: > > > > "Make the scan faster" > > "Make the scan incremental and automatic" > > "Make it not bl

Re: [DISCUSS] Future of MVs

2020-07-01 Thread Benedict Elliott Smith
I humbly suggest these are the wrong questions to ask. Instead, two sides of just one question matter: how did we miss these problems, and what would we have needed to do procedurally to have not missed it. Whatever it is, we need to do it now to have confidence other things were not missed, a

Re: [DISCUSS] Future of MVs

2020-07-01 Thread Joshua McKenzie
Which questions and how we frame it aside, it's clear we have some foundational thinking to do, articulate, and agree upon as a project before we can reasonably make decisions about deprecation, promotion, or inclusion of features in the project. Is that fair? If so, I propose we set this thread

Re: [DISCUSS] Future of MVs

2020-07-01 Thread Jon Haddad
I think coming up with a formal comprehensive guide for determining if we can merge these sort of huge impacting features is a great idea. I'm also on board with applying the same standard to the experimental features. On Wed, Jul 1, 2020 at 1:45 PM Joshua McKenzie wrote: > Which questions and

Re: [DISCUSS] Future of MVs

2020-07-01 Thread David Capwell
+1 On Wed, Jul 1, 2020 at 1:55 PM Jon Haddad wrote: > I think coming up with a formal comprehensive guide for determining if we > can merge these sort of huge impacting features is a great idea. > > I'm also on board with applying the same standard to the experimental > features. > > On Wed, Jul

Re: [DISCUSS] Future of MVs

2020-07-01 Thread Nate McCall
> > > > If so, I propose we set this thread down for now in deference to us > articulating the quality bar we set and how we achieve it for features in > the DB and then retroactively apply them to existing experimental features. > Should we determine nobody is stepping up to maintain an > experime

Re: [DISCUSS] Future of MVs

2020-07-01 Thread Joshua McKenzie
Plays pretty cleanly into the "have a test plan" we modded in last month. +1 On Wed, Jul 1, 2020 at 6:43 PM Nate McCall wrote: > > > > > > > > If so, I propose we set this thread down for now in deference to us > > articulating the quality bar we set and how we achieve it for features in > > the

Moving forward towards our best release yet

2020-07-01 Thread Jeremy Hanna
I've been in the Cassandra community for about 10 years now and I've seen a lot of ups and downs. I care deeply about both the project and the people interacting on the project personally. I consider many of you to be good friends. Regardless of the history that's caused some friction on rece