b3a4efd587
This reverts commit a547c523c2 or #2281
The current implementation can cause panics and performance degradation.
I will bring this back with more testing in
https://github.com/lancedb/lancedb/pull/2311
<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->
## Summary by CodeRabbit
- **Documentation**
- Enhanced clarity on read consistency settings with updated
descriptions and default behavior.
- Removed outdated warnings about eventual consistency from the
troubleshooting guide.
- **Refactor**
- Streamlined the handling of the read consistency interval across
integrations, now defaulting to "None" for improved performance.
- Simplified internal logic to offer a more consistent experience.
- **Tests**
- Updated test expectations to reflect the new default representation
for the read consistency interval.
- Removed redundant tests related to "no consistency" settings for
streamlined testing.
<!-- end of auto-generated comment: release notes by coderabbit.ai -->
---------
Co-authored-by: coderabbitai[bot] <136622811+coderabbitai[bot]@users.noreply.github.com>
1.9 KiB
Getting help
The following sections provide various diagnostics and troubleshooting tips for LanceDB. These can help you provide additional information when asking questions or making error reports.
For trouble shooting, the best place to ask is in our Discord, under the relevant language channel. By asking in the language-specific channel, it makes it more likely that someone who knows the answer will see your question.
Common issues
- Multiprocessing with
forkis not supported. You should usespawninstead.
Enabling logging
To provide more information, especially for LanceDB Cloud related issues, enable
debug logging. You can set the LANCEDB_LOG environment variable:
export LANCEDB_LOG=debug
You can turn off colors and formatting in the logs by setting
export LANCEDB_LOG_STYLE=never
Explaining query plans
If you have slow queries or unexpected query results, it can be helpful to
print the resolved query plan. You can use the explain_plan method to do this:
- Python Sync: [LanceQueryBuilder.explain_plan][lancedb.query.LanceQueryBuilder.explain_plan]
- Python Async: [AsyncQueryBase.explain_plan][lancedb.query.AsyncQueryBase.explain_plan]
- Node @lancedb/lancedb: LanceQueryBuilder.explainPlan
To understand how a query was actually executed—including metrics like execution time, number of rows processed, I/O stats, and more—use the analyze_plan method. This executes the query and returns a physical execution plan annotated with runtime metrics, making it especially helpful for performance tuning and debugging.
- Python Sync: [LanceQueryBuilder.analyze_plan][lancedb.query.LanceQueryBuilder.analyze_plan]
- Python Async: [AsyncQueryBase.analyze_plan][lancedb.query.AsyncQueryBase.analyze_plan]
- Node @lancedb/lancedb: LanceQueryBuilder.analyzePlan