My advice to avoid them is based on the issues that have been filed in Jira. Benjamin Roth is one of the only people talking about his MV usage, and has filed a few JIRAs discussing their problems when bootstrapping new nodes, as well as issues repairing.
https://issues.apache.org/jira/browse/CASSANDRA-12730?jql=project%20%3D%20CASSANDRA%20and%20reporter%20%3D%20brstgt%20and%20text%20~%20%22materialized%22 They also can't be altered: https://issues.apache.org/jira/browse/CASSANDRA-9736 They may be less performant than managing the data yourself: https://issues.apache.org/jira/browse/CASSANDRA-10295, https://issues.apache.org/jira/browse/CASSANDRA-10307 They're not as flexible as your own tables: https://issues.apache.org/jira/browse/CASSANDRA-9928, https://issues.apache.org/jira/browse/CASSANDRA-11194, https://issues.apache.org/jira/browse/CASSANDRA-12463 They break incremental repair if you use CDC: https://issues.apache.org/jira/browse/CASSANDRA-12888 I don't know why DataStax advises using them. Perhaps ask them? Jon On Thu, Feb 16, 2017 at 7:57 AM Micha <mich...@fantasymail.de> wrote: > > > On 16.02.2017 16:33, Jonathan Haddad wrote: > > > > Regarding MVs, do not use the ones that shipped with 3.x. They're not > > ready for production. Manage it yourself by using a second table and > > inserting a second record there. > > > > Out of interest... there is a slight discrepance between the advice not > to use mv and the docu about the feature on the datastax side. Or do I > have to use another cassandra version (instead of 3.9)? > >
