The general view of the community is that you should *NOT* use them in production, due to multiple serious outstanding issues (see Jira). We used them quite a bit when they first came out and have since rolled back all uses except for the absolute most basic cases (ex: a table with 30K rows that isn’t updated). If we were to do it over, we would not use them at all.
- Max > On Feb 28, 2020, at 7:07 am, Tobias Eriksson <tobias.eriks...@qvantel.com> > wrote: > > Hi > A debate has surfaced in my company, whether to keep or remove Materialized > Views > The Datastax FAQ says sure thing, go ahead and use it > https://docs.datastax.com/en/dse/5.1/cql/cql/cql_using/faqMV.html > <https://docs.datastax.com/en/dse/5.1/cql/cql/cql_using/faqMV.html> > But know the limitations > https://docs.datastax.com/en/dse/5.1/cql/cql/cql_using/knownLimitationsMV.html > > <https://docs.datastax.com/en/dse/5.1/cql/cql/cql_using/knownLimitationsMV.html> > and best practices > https://docs.datastax.com/en/dse/5.1/cql/cql/cql_using/bestPracticesMV.html > <https://docs.datastax.com/en/dse/5.1/cql/cql/cql_using/bestPracticesMV.html> > > What is the community take on using MV(Materialized Views) in production ? > > -Tobias
