Files
lancedb/docs/web/troubleshooting.mdx
T
Jack Ye 4015560b83 docs: restructure around the three API surfaces
The Documentation tab now reads as a manual over Python, TypeScript and SQL
rather than a Python guide with SQL bolted on.

Basics replaces the Catalog section: what the catalog holds, what each API
surface can do, jobs, agentic skills, and what Lance is. Management is new and
is the CRUD and listing reference for every catalog object, with a column per
language so the gaps are visible -- TypeScript has no function or SQL methods,
SQL needs a deployment.

Search becomes Query and gains a SELECT reference, since an analytical query is
a query whether it came from a builder or a statement.

Jobs is new. Every long-running operation already returned the same handle from
an _async method; nothing documented it.

The SQL function reference gains what Lance registers on top of DataFusion:
contains_tokens, backed by the FTS index, and the JSON accessors, backed by a
JSON scalar index. Geospatial st_* functions are behind a build feature LanceDB
does not ship, which is now stated rather than left to a confusing error.

Removes the Geneva pages' orphaned snippets, merges FTS Examples into Full-Text
Search, and splits Query Optimization into Explain and Explain Analyze.
2026-09-09 22:20:19 -07:00

35 lines
1.3 KiB
Plaintext

---
title: "Troubleshooting"
sidebarTitle: "Troubleshooting"
description: "Tips for troubleshooting basic LanceDB issues."
icon: "tools"
---
## Frequently-asked questions {#frequently-asked-questions}
For commonly asked questions about LanceDB, please refer to our [FAQ section](/faq).
## Getting technical support {#getting-technical-support}
If you're using LanceDB OSS, the best place to get help is in our
[Discord community](https://discord.gg/AUEWnJ7Txb),
under the relevant language channel for Python, TypeScript, or Rust.
By asking in the language-specific channel, you can get help from the community
and our engineering team.
If you are a LanceDB Enterprise user, please contact our support team at [support@lancedb.com](mailto:support@lancedb.com) for dedicated assistance.
## General issues {#general-issues}
### Slow or unexpected query results {#slow-or-unexpected-query-results}
If you have slow queries or unexpected query results, it can be helpful to
print the resolved query plan.
LanceDB provides two powerful tools for query analysis and optimization: `explain_plan` and `analyze_plan`.
Read the full guides on [Explain](/search/explain) and [Explain Analyze](/search/explain-analyze).
### The Python multiprocessing module {#the-python-multiprocessing-module}
Multiprocessing with `fork` is not supported. You should use `spawn` instead.