mirror of
https://github.com/lancedb/lancedb.git
synced 2026-10-30 15:26: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.4 KiB
Plaintext
34 lines
1.4 KiB
Plaintext
---
|
|
title: "Distributed search"
|
|
sidebarTitle: "Distributed search"
|
|
description: "How LanceDB Enterprise distributes index execution and table-data reads."
|
|
icon: "network-wired"
|
|
availability:
|
|
oss: unavailable
|
|
enterprise: available
|
|
summary: >-
|
|
LanceDB Enterprise distributes index execution and table-data reads across
|
|
executors. LanceDB Embedded executes searches in the application process.
|
|
---
|
|
|
|
Distributed search spreads index execution, table-data reads, and caching across
|
|
multiple serving machines in LanceDB Enterprise. Query nodes plan queries and
|
|
combine results. Executors cache index structures and table data and execute
|
|
the distributed work. See [Enterprise architecture](/enterprise/architecture).
|
|
|
|
## Embedded search {#embedded-search}
|
|
|
|
LanceDB Embedded runs inside your application process. It searches indexes and reads
|
|
table data using that process's resources, including its index cache. Reading a
|
|
table from object storage does not by itself distribute query execution across
|
|
machines.
|
|
|
|
## Search interfaces {#search-interfaces}
|
|
|
|
The shared search guides describe the query APIs and index settings:
|
|
|
|
- [Vector search](/search/vector-search) and [vector indexes](/indexing/vector-index).
|
|
- [Full-text search](/search/full-text-search) and [FTS indexes](/indexing/fts-index).
|
|
- [Filtering](/search/filtering) and [scalar indexes](/indexing/scalar-index).
|
|
- [Query plans](/search/explain) for inspecting execution and runtime measurements.
|