From 65ed41333bbd628df52d1d681f85c8f8c06ddc20 Mon Sep 17 00:00:00 2001 From: Jack Ye Date: Fri, 4 Sep 2026 00:06:54 -0700 Subject: [PATCH] docs: distinguish this materialized view from the Enterprise one Both the lancedb client and the geneva client expose `create_materialized_view`, and they are not the same feature. The page said materialized views are local only, which is true of this client and misleading for anyone on Enterprise, where views are created through geneva and refreshed on the cluster. Found by assembling the combined site and reading the Geneva pages against the new ones: they described the same call as distributed and Enterprise while this one described it as raising. Both were accurate about their own client and neither said which client it meant. --- .../feature-engineering/materialized-views.mdx | 18 ++++++++++++------ 1 file changed, 12 insertions(+), 6 deletions(-) diff --git a/docs/web/feature-engineering/materialized-views.mdx b/docs/web/feature-engineering/materialized-views.mdx index b6d267ae4..966bc052c 100644 --- a/docs/web/feature-engineering/materialized-views.mdx +++ b/docs/web/feature-engineering/materialized-views.mdx @@ -77,15 +77,21 @@ them twice — so a retry loop around `refresh()` is safe. ## Local databases only {#availability} -Materialized views are supported on **local databases**. Calling -`create_materialized_view` on a remote connection raises `NotImplementedError`. +**This** materialized view — the one created through `lancedb.connect(...)` — is +supported on local databases only. Calling `create_materialized_view` on a +remote `db://` connection raises `NotImplementedError`. -This is the reverse of [functions](/feature-engineering/functions), which run -only against Cloud and Enterprise. If you are deriving tables on a remote -database, a [computed column](/feature-engineering/computed-columns) filled by a -server job is usually the closer fit. +Enterprise has its own materialized views, created through a different client +with the same method name. If you are working against an Enterprise deployment, +that is the one you want; see the Enterprise feature engineering documentation. +The two are not the same feature and the method name is unfortunately shared, so +it is worth being sure which client you are holding. +Note the direction, which is the reverse of +[functions](/feature-engineering/functions): those run only against Cloud and +Enterprise and raise locally. Neither mechanism is available on both. + ## Working with the view {#working-with-the-view} `view.table()` returns the underlying table for querying, indexing, or search.