Managing Materialized views

A materialized view is a table built from data in another table with a new primary key and new properties. Queries are optimized by the primary key definition. Standard practice is to create a table for the query, and create a new table with the same data if a different query is needed. Client applications then manually update the additional tables as well as the original. In the materialized view, data is updated automatically by changes to the source table.

Materialized views are not available on Astra serverless databases. For more, see Astra database limits.

Understanding materialized views

Learn how DSE propagates updates from a base table to its materialized views.

Known limitations of materialized views

The following limitations are known for materialized views.

Creating a materialized view

Create materialized views with the CREATE MATERIALIZED VIEW command.

Altering a materialized view

Alter the properties of a materialized view with the ALTER MATERIALIZED VIEW command.

ropping a materialized view

Drop materialized views with the DROP MATERIALIZED VIEW command.

Frequently asked questions about materialized views

Answers to the most common questions regarding usage of materialized views.

Was this helpful?

Give Feedback

How can we improve the documentation?

© 2024 DataStax | Privacy policy | Terms of use

Apache, Apache Cassandra, Cassandra, Apache Tomcat, Tomcat, Apache Lucene, Apache Solr, Apache Hadoop, Hadoop, Apache Pulsar, Pulsar, Apache Spark, Spark, Apache TinkerPop, TinkerPop, Apache Kafka and Kafka are either registered trademarks or trademarks of the Apache Software Foundation or its subsidiaries in Canada, the United States and/or other countries. Kubernetes is the registered trademark of the Linux Foundation.

General Inquiries: +1 (650) 389-6000, info@datastax.com