mirror of
https://github.com/lancedb/lancedb.git
synced 2026-10-30 23:36: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>
37 lines
1.4 KiB
Plaintext
37 lines
1.4 KiB
Plaintext
---
|
|
title: "Support"
|
|
sidebarTitle: "Support"
|
|
description: "Where to get help: community Discord for LanceDB Embedded (open source), dedicated support for LanceDB Enterprise."
|
|
icon: circle-question
|
|
keywords: ["support", "help", "discord", "community"]
|
|
---
|
|
|
|
## LanceDB Embedded (open source) {#oss}
|
|
|
|
For a quick question, the
|
|
[Discord community](https://discord.gg/AUEWnJ7Txb) has channels for
|
|
Python, TypeScript and Rust where you can ask the community for help.
|
|
|
|
Use GitHub for discussions and issues that others can search and follow:
|
|
|
|
| | |
|
|
| --- | --- |
|
|
| [GitHub Discussions](https://github.com/lancedb/lancedb/discussions) | Open-ended questions, design questions, "what's the right way to do X" |
|
|
| [GitHub Issues](https://github.com/lancedb/lancedb/issues) | A specific bug, or a feature request |
|
|
|
|
## LanceDB Enterprise {#enterprise}
|
|
|
|
<Badge color="red">Enterprise</Badge> Contact your support team directly at
|
|
[support@lancedb.com](mailto:support@lancedb.com) for dedicated assistance.
|
|
|
|
## What to include {#what-to-include}
|
|
|
|
A faster answer usually depends on the same handful of details:
|
|
|
|
| | |
|
|
| --- | --- |
|
|
| SDK and version | `lancedb.__version__` (Python), `package.json` (TypeScript), the crate version (Rust) |
|
|
| Connection type | embedded path, or a `db://` deployment |
|
|
| The exact error | full traceback or error message, not a paraphrase |
|
|
| A minimal repro | the smallest table schema and call that reproduces it |
|