rust/lancedb
1
0
Fork 0
mirror of https://github.com/lancedb/lancedb.git synced 2026-10-14 07:42:28 +00:00
Code Issues Packages Projects Releases Wiki Activity

docs: say materialized views are off by default on a deployment

Browse Source 
The deployment notes called materialized views experimental. Nothing
published says so; the word came from one comment in Sophon's create
handler. What Sophon's source does establish is that a deployment serves
materialized views only with derived_compute_enabled, which is off by
default, so the pages now say that instead.
This commit is contained in:
Brendan Clement
2026-10-06 21:03:34 -07:00
parent bcd68c16e1
commit 0e9dc14d01
3 changed files with 7 additions and 7 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/web/feature-engineering/materialized-views.mdx
+3 -3
View File
@@ -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.
docs/web/management/materialized-view.mdx
+1 -1
View File
@@ -77,7 +77,7 @@ rows. Both are properties; on an async view, the definition is read with
<Badge color="red">Enterprise</Badge> `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).
docs/web/sql/ddl/materialized-view.mdx
+3 -3
View File
@@ -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.
<Note>
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.
</Note>
## CREATE MATERIALIZED VIEW {#create}