mirror of
https://github.com/lancedb/lancedb.git
synced 2026-10-12 23:02:28 +00:00
Jack Ye
21786845a7
FAQ content is redistributed into the pages it actually belongs to: license and Parquet-comparison notes into the Lance format page, scale guidance into Architecture, index-necessity and refine_factor guidance into the vector index page, the multiprocessing/fork gotcha into SDKs and SQL, and the weak-consistency recommendation into Consistency. General query-performance issues are dropped since Explain and Explain Analyze already cover that ground. The new Support page under Deployment carries the OSS Discord and Enterprise support-email channels that used to live in Troubleshooting.
31 lines
1.1 KiB
Plaintext
31 lines
1.1 KiB
Plaintext
---
|
|
title: "Support"
|
|
sidebarTitle: "Support"
|
|
description: "Where to get help: community Discord for OSS, dedicated support for Enterprise."
|
|
icon: circle-question
|
|
keywords: ["support", "help", "discord", "community"]
|
|
---
|
|
|
|
## LanceDB OSS {#oss}
|
|
|
|
The best place to get help is the
|
|
[Discord community](https://discord.gg/AUEWnJ7Txb), under the relevant
|
|
language channel for Python, TypeScript, or Rust. Asking in the
|
|
language-specific channel reaches both the community and the engineering team.
|
|
|
|
## 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 |
|