mirror of
https://github.com/lancedb/lancedb.git
synced 2026-10-30 15:26:52 +00:00
Jack Ye
ddb318567a
## Summary - Complete the SQL reference: `ATTACH DATABASE`, the `CHANGES` clause, and `dedupe()`/`duplicate_pairs()` (verified against current sophon source; these were recently renamed from `vector_dedup`/`vector_duplicate_pairs`). Fix the blob-column default-projection claim and add the previously undocumented `blob_descriptor()`. - Enrich the gated Functions draft (still `.mintignore`'d, pre-release): chained Functions over blob outputs, GPU-produced blobs, Secrets, multi-input/output binding, `code=[module]` packaging. - Upgrade the materialized-view and computed-column auto-refresh drafts with precise, verified catch-up semantics, and add the missing `ALTER MATERIALIZED VIEW` / `CREATE ... WITH(...)` sections (also gated — the automatic-refresh scheduler is still dev/staging-only). - Thread one running example (video frames → GPU extract/caption → dedup → auto-refreshing materialized view) through Functions, materialized views, and the LeRobotDataset integration guide instead of a separate tutorial. - Rename "LanceDB OSS"/"OSS" to "LanceDB Embedded"/"Embedded" throughout (52 files); activate the existing availability-comparison mechanism on `basics/offerings.mdx` for a full feature-by-feature comparison table.
31 lines
1.3 KiB
Plaintext
31 lines
1.3 KiB
Plaintext
---
|
|
title: "Distributed search"
|
|
sidebarTitle: "Distributed search"
|
|
description: "How LanceDB Enterprise distributes index execution and table-data reads."
|
|
icon: "network-wired"
|
|
availability:
|
|
embedded: unavailable
|
|
enterprise: available
|
|
---
|
|
|
|
Distributed search spreads index execution, table-data reads, and caching across
|
|
multiple serving machines in LanceDB Enterprise. Query nodes plan queries and
|
|
combine results. Plan executors cache index structures and table data and execute
|
|
the remote work. See [Architecture](/#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.
|