mirror of
https://github.com/lancedb/lancedb.git
synced 2026-10-13 07:12:27 +00:00
Jack Ye
19f8f396ec
Ten merges and renames, all in one direction: fewer pages, each covering a whole subject. Table absorbs schema evolution and versioning. Vector search absorbs multi-vector. Explain absorbs explain analyze. Reranking was seven pages -- an overview and six rerankers of a few dozen lines each -- and is now one. The vector index page absorbs quantization, which was only ever a parameter of it. Indexing moves to Manage, where the other catalog objects are. The operational half stays in Operate as one Indexing page, absorbing GPU indexing -- which was filed in sophon despite importing lancedb's snippets and being mostly open-source content with one Enterprise-badged section. Performance was a single page aggregating tips for four unrelated operations, which is hard to keep current. Each section now sits with the operation it is about: ingestion tips on Insert, index tips on Indexing, compaction tips on Compaction, query tips on Search. Data Types leaves Concepts. The type reference belongs in the SQL reference, which already described the same types from the query side; Table now carries a short summary that points there. The multimodal material it had absorbed is its own page again, since storing blobs is a task rather than a type definition. Query becomes Semantic Search, Branches becomes Branch, and the Enterprise Security page becomes Compliance. Redirects cover every moved URL, and 30 files were repointed at the merged anchors.
35 lines
1.3 KiB
Plaintext
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).
|
|
|
|
### The Python multiprocessing module {#the-python-multiprocessing-module}
|
|
Multiprocessing with `fork` is not supported. You should use `spawn` instead.
|