Enterprise only
A materialized view stores a query’s result as rows, kept current by a refresh.
It is the counterpart to a view, which stores only the query.
Materialized views are off by default in LanceDB Enterprise and have to be enabled
there. Which statements and query shapes a deployment accepts, whether it needs
the source table to have stable row ids, and how it refreshes a view depend on
its LanceDB Enterprise version and configuration.
CREATE MATERIALIZED VIEW
SHOW MATERIALIZED VIEWS
namespace_path, a compact JSON array
of parent namespace components ([] for root), and name, the unqualified
object name. Omitting IN lists all authorized namespaces in the current database;
IN team$ml selects that exact path without a database qualifier; IN public selects
the current database’s root. Listings require the relevant database and
namespace USAGE privileges.
The listing contains identifiers; use DESCRIBE MATERIALIZED VIEW for its defining query and refresh metadata.
Page through results using LIMIT n [FROM '<page-token>']. Read the opaque
lancedb.next_page_token from the Arrow result schema metadata and pass it back
unchanged with the same object type and scope. Stop when no token is returned;
a short or empty page can still carry a continuation. See
catalog listing pagination.
Refreshing one
Dropping one
DROP TABLE, even though a materialized view is
a table underneath. For the same reason, dropping one removes stored rows,
unlike dropping a view.
Enterprise job type for a refresh:
sql. Dropping, by contrast, runs the
same underlying job as dropping any table, drop_table or drop_object.What to read next
Materialized View
Creating one from the SDK.
Refresh a materialized view
How a refresh works, in LanceDB Enterprise.