mirror of
https://github.com/lancedb/lancedb.git
synced 2026-11-03 09:16:52 +00:00
Will JonesandClaude Opus 5.5
4d7a64712f
## Summary Adopts the product terminology guide across the docs site pages, SDK docstrings and error messages. "LanceDB OSS" and local mode become **LanceDB Embedded**. "Remote" as the execution model becomes **LanceDB Distributed**, which LanceDB Enterprise provides. Where free vs paid is the point, pages contrast "LanceDB Embedded (open source)" with "LanceDB Enterprise". This is a first trial of the Embedded name, so reviewers can judge it in context. - **Embedded vs Distributed** for where execution runs (`optimize()`, consistency, branching, maintenance). Main pages define it once: "LanceDB Enterprise runs LanceDB Distributed: …" - **LanceDB Cloud** is kept only for legacy-Cloud specifics (`db://` region, the brute-force KNN limit) and marked legacy. "Cloud and Enterprise" becomes Enterprise or Distributed. - **Plan executor** becomes "executor" or the fleet name. - **Error messages** change, e.g. `optimize is not supported for remote tables.` → `... in LanceDB Distributed.` Tests that match on them are updated. - **Vale rules** (`EmbeddedName`, `OSSProduct`, `RemoteExecution`, `DistributedEnterprise`, `LegacyCloud`, `InternalNames`) enforce the terms in prose. Unchanged: identifiers (`availability.oss`, the `remote` module and feature, `RemoteTable`, `db://`), heading anchors, internal code comments, and Geneva. ## Evidence - Rust lib tests for the changed messages and the Python tests in `test_remote_db.py`, `test_materialized_views.py` and `test_table.py` pass locally. - Not run locally: - The Node tests: `remote.test.ts` and `table.test.ts` have updated assertions. - Vale. - The `experimental_functions`-marked materialized-view tests. - `docs/src` API reference was hand-edited to match the docstrings rather than regenerated. ## Merge Risk **Door:** two-way; prose and message text only. **Blast Radius:** `docs`, `error-messages`: callers matching on old error strings would break. Companion PRs: lancedb/docs (assembler labels, STYLE.md) and sophon (Enterprise pages). 🤖 Generated with [Claude Code](https://claude.com/claude-code) --------- Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
34 lines
1.1 KiB
Plaintext
34 lines
1.1 KiB
Plaintext
---
|
|
title: "LanceDB Enterprise"
|
|
sidebarTitle: "Overview"
|
|
description: "What a deployment adds over LanceDB Embedded."
|
|
icon: building
|
|
keywords: ["enterprise", "deployment", "cluster"]
|
|
---
|
|
|
|
<Badge color="red">Enterprise</Badge>
|
|
|
|
This page describes a LanceDB Enterprise capability. The embedded form
|
|
of LanceDB has no server to provide it. See
|
|
[Architecture](/architecture) for what differs between the two.
|
|
|
|
LanceDB Enterprise runs the lakehouse as a service: a control plane for
|
|
configuration, identity and policy; a data plane serving reads and writes; and
|
|
indexers building indexes and compacting outside the request path.
|
|
|
|
What it adds over the embedded form:
|
|
|
|
| | |
|
|
| --- | --- |
|
|
| [SQL](/sql) | an Arrow Flight SQL endpoint |
|
|
| [Jobs](/basics/jobs) | server-side work with ids, status and events |
|
|
| [Authorization](/governance/authorization) | per-object grants |
|
|
| Scale | a cluster rather than your process |
|
|
|
|
{/*
|
|
Draft for the Functions release. Add this row to the table above, after SQL:
|
|
| [Functions](/management/function) | Python running on workers |
|
|
*/}
|
|
|
|
See [Architecture](/architecture) for the two shapes side by side.
|