diff --git a/docs/web/feature-engineering/materialized-views.mdx b/docs/web/feature-engineering/materialized-views.mdx index 15dcf64ce..b0e7e142b 100644 --- a/docs/web/feature-engineering/materialized-views.mdx +++ b/docs/web/feature-engineering/materialized-views.mdx @@ -79,9 +79,9 @@ and `REFRESH MATERIALIZED VIEW` -- and the work runs on the cluster rather than in your process. `source_version` is for local views only; the SDK refuses it on a remote refresh. -Materialized views are experimental on a deployment, which has to have them -enabled. How its refresh works -- rebuilding the whole view, as above, or -reconciling what changed in the source -- depends on its LanceDB Enterprise +Materialized views are off by default on a deployment and have to be enabled +there. How a deployment refreshes a view -- rebuilding the whole view, as above, +or reconciling what changed in the source -- depends on its LanceDB Enterprise version and configuration, and so do the options [`REFRESH MATERIALIZED VIEW`](/sql/dml/refresh#refresh-materialized-view) accepts. diff --git a/docs/web/management/materialized-view.mdx b/docs/web/management/materialized-view.mdx index 71b7332ef..bc7aa92c5 100644 --- a/docs/web/management/materialized-view.mdx +++ b/docs/web/management/materialized-view.mdx @@ -77,7 +77,7 @@ rows. Both are properties; on an async view, the definition is read with Enterprise `create_materialized_view` works on a `db://` connection as well as a local one. There the SDK creates and refreshes the view through SQL, and the work runs on the cluster rather than in your -process. Materialized views are experimental on a deployment and have to be +process. Materialized views are off by default on a deployment and have to be enabled there; see [Against a deployment](/feature-engineering/materialized-views#availability). diff --git a/docs/web/sql/ddl/materialized-view.mdx b/docs/web/sql/ddl/materialized-view.mdx index eeb053639..9c68af2f2 100644 --- a/docs/web/sql/ddl/materialized-view.mdx +++ b/docs/web/sql/ddl/materialized-view.mdx @@ -12,9 +12,9 @@ A materialized view stores a query's result as rows, kept current by a refresh -- the counterpart to a [view](/sql/ddl/view), which stores only the query. -Materialized views are experimental on a deployment, which has to have them -enabled. Which statements and query shapes a deployment accepts, and how its -refresh works, depend on its LanceDB Enterprise version and configuration. +Materialized views are off by default on a deployment and have to be enabled +there. Which statements and query shapes a deployment accepts, and how it +refreshes a view, depend on its LanceDB Enterprise version and configuration. ## CREATE MATERIALIZED VIEW {#create}