Files
lancedb/docs/src/js/interfaces/ConnectionOptions.md
T
Will JonesandClaude Opus 5.5 4d7a64712f docs: adopt Embedded/Distributed terminology across docs and SDKs (#4713)
## 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>
2026-10-28 14:04:41 -07:00

2.8 KiB

@lancedb/lancedb • Docs


@lancedb/lancedb / ConnectionOptions

Interface: ConnectionOptions

Properties

apiKey?

optional apiKey: string;

(For LanceDB Enterprise or LanceDB Cloud only): the API key to use.

Can also be set via the environment variable LANCEDB_API_KEY.


clientConfig?

optional clientConfig: ClientConfig;

(For LanceDB Enterprise or LanceDB Cloud only): configuration for the HTTP client.


hostOverride?

optional hostOverride: string;

(For LanceDB Enterprise only): the host of the LanceDB Enterprise deployment to connect to.


manifestEnabled?

optional manifestEnabled: boolean;

(For LanceDB Embedded only): use directory namespace manifests as the source of truth for table metadata. Existing directory-listed root tables are migrated into the manifest on access.


namespaceClientProperties?

optional namespaceClientProperties: Record<string, string>;

(For LanceDB Embedded only): extra properties for the backing namespace client used by manifest-enabled native connections.


oauthConfig?

optional oauthConfig: NativeOAuthConfig;

(For LanceDB Enterprise only): OAuth configuration for IdP-based authentication (e.g., Azure Entra ID). When set, token acquisition and refresh are handled entirely in Rust. TypeScript users should pass the public OAuthConfig type exported from @lancedb/lancedb.


readConsistencyInterval?

optional readConsistencyInterval: number;

The interval, in seconds, at which to check for updates to the table from other processes. If None, then consistency is not checked. For performance reasons, this is the default. For strong consistency, set this to zero seconds. Then every read will check for updates from other processes. As a compromise, you can set this to a non-zero value for eventual consistency. If more than that interval has passed since the last check, then the table will be checked for updates. Note: this consistency only applies to read operations. Write operations are always consistent.

Stronger consistency is not free. The smaller the interval, the more often each read pays the cost of checking for updates against object storage, raising per-read latency and cost.


region?

optional region: string;

(For LanceDB Cloud only): the region to use for LanceDB Cloud (legacy). Defaults to 'us-east-1'.


session?

optional session: Session;

(For LanceDB Embedded only): the session to use for this connection. Holds shared caches and other session-specific state.


storageOptions?

optional storageOptions: Record<string, string>;

(For LanceDB Embedded only): configuration for object storage.

The available options are described at https://docs.lancedb.com/storage/