> While at TLP, I helped numerous customers move off of MVs, mostly because > they affected stability of clusters in a horrific way. The most telling > project involved helping someone create new tables to manage 1GB of data > because the views performed so poorly they made the cluster unresponsive > and unusable.
The documented way to report bugs: https://cassandra.apache.org/doc/latest/bugs.html# with JIRA, Version, Environment. > As we move forward with the 4.0 release, we should consider this an opportunity to deprecate materialized views, and remove them in 5.0. While the community is focusing on 4.0 and unable to review CEP/Improvements, should we discuss it when community is ready to discuss about CEP/Improvements? > We should take this opportunity to learn from the mistake and raise the bar > for new features to undergo a much more thorough run the wringer before > merging. Agreed to learn from mistakes, but there are still users using MV. I think it's more responsible to work with users to improve MV on their use cases. > Am I missing a JIRA > that can magically fix the issues with performance, availability & > correctness? Is there any formal discussion/analysis about things being impossible to fix/improve? On Wed, 1 Jul 2020 at 04:23, Dinesh Joshi <djo...@apache.org> wrote: > > On Jun 30, 2020, at 12:43 PM, Jon Haddad <j...@jonhaddad.com> wrote: > > > > As we move forward with the 4.0 release, we should consider this an > > opportunity to deprecate materialized views, and remove them in 5.0. We > > should take this opportunity to learn from the mistake and raise the bar > > for new features to undergo a much more thorough run the wringer before > > merging. > > I'm in favor of marking them as deprecated and removing them in 5.0. If > someone steps up and can fix them in 5.0, then we always have the option of > accepting the fix. > > Dinesh > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org > For additional commands, e-mail: dev-h...@cassandra.apache.org > >
