On 2017-07-16 21:22 (-0700), kurt greaves <k...@instaclustr.com> wrote: > wall of text inc. > *tl;dr: *Aiming to come to some conclusions about what we are doing with > MV's and how we are going to make them stable in production. But really > just trying to raise awareness/involvement for MV's. >
I share your frustration, for what it's worth. And Ben's, too. That doesn't necessarily count for much, I'm afraid, but I sympathize. > It seems we've got an excess of MV bugs that pretty much make them > completely unusable in production, or at least incredibly risky and also > limited. It also appears that we don't have many people totally across MV's > either (or at least a lack of people currently looking at them). To avoid > us "forgetting" about MV's I'd like to raise the current issues and get > opinions on the direction we should go with MV's. I know historically there > was a lot of discussion about this, but it seems a lot of the originally > involved are currently less involved, and thus before making wild changes > to MV's it might be worth going back to the start and think through the > original requirements and implementation. > > > If anyone has been working on any of these tickets and no longer is able > to, either update the ticket or let me know and I'll either take over/find > some other poor soul to have a stab at it. > It would also be nice to get some volunteers who are familiar with MV's to > review the above tickets. Anyone want to admit to running them in prod? Any committers with an MV install base? Any non-trivial use cases? > > > My general advice these days is for users to steer clear of MV's for the > moment, however we have no clear plan for when these will really be stable. > I think as some of the changes to fix MV's may potentially require a major > version change, we should at least aim to get all those in for 4.0 > (although still need to figure out what exactly these issues are). > Interested to hear peoples thoughts. I think you're probably right on here. I think they may work for people with suitably simple use cases (append only, no delete, writes with strong consistency, and use single token or few tokens per node). I think the more clear point is that we need people willing to help step up and fix it. I don't use them in prod, and I don't actually know anyone who does (though clearly a few folks do, including the three or four folks who seem to actually be working on the tickets), so perhaps the real solution is we need to be more aggressive about nominating and electing committers who are willing to spend some attention on MVs. --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org For additional commands, e-mail: dev-h...@cassandra.apache.org
