mirror of
https://github.com/lancedb/lancedb.git
synced 2026-11-13 22:26:53 +00:00
Jack YeandClaude Sonnet 5
de95ed3f6d
A broad documentation pass across the areas LanceDB Enterprise and Embedded diverge on most: **Data Curation** -- GPU Function execution, Slurm scheduling (and what Slurm is, for readers new to it), blob late materialization as its own page, joins, aggregation/profiling, sampling, near-duplicate detection, chunking, distributed shuffle, and IVF-partition clustering. **Feature Engineering** -- computed columns and materialized views, restructured to lead with the Function-based path and show the SQL form side by side with Python throughout; a single Auto Refresh page instead of duplicating scheduling details on every refresh page; adaptive execution; checkpointing; GPU and Slurm placement for refresh workers; a Training Cache page for the PyTorch data loader's automatic cache benefit. **Security & Governance** -- an Audit Log reference (schema, access, grants), Secrets promoted to an ordinary catalog object with their own SQL DDL and a vending/rotation guide, and privilege-table fixes verified against the authorization source. **Deployment & Maintenance** -- Horizontal Scaling and OpenTelemetry moved into a real Deployment area; Automated Cleanup folded into Intelligent Auto-Maintenance (every other maintenance decision already lived there); RTE Compaction and Advanced Conflict Resolution documented in depth. **Landing page** -- the Enterprise feature comparison table reorganized (several redundant or stale rows removed, several new areas added), and the "why Enterprise" bullets replaced with ones tied to a concrete page (Performance, Scale, Fault tolerance, Multicloud deployment, Simplify operations) instead of vague promises. Plus a full pass addressing lancedb-gatekeeper's review: a real test-safety bug (a quickstart test could silently overwrite and delete a deployment's own `frames` table), a fabricated SQL statement with no backing implementation, an actual dedup-guarantee bug in `take_row_ids`, and dozens of documentation-accuracy fixes verified against source rather than taken on faith -- each either fixed, or left with an explicit note on why it needs a feature or deployment owner's sign-off instead of being guessed at. 🤖 Generated with [Claude Code](https://claude.com/claude-code) https://claude.ai/code/session_018PXMCbRH6i5w47TsjeEUMT --------- Co-authored-by: Claude Sonnet 5 <noreply@anthropic.com>
41 lines
1.5 KiB
Plaintext
41 lines
1.5 KiB
Plaintext
---
|
|
title: "Support"
|
|
sidebarTitle: "Support"
|
|
description: "Where to get help: community Discord and email for LanceDB Embedded, dedicated support for LanceDB Enterprise."
|
|
icon: circle-question
|
|
keywords: ["support", "help", "discord", "community"]
|
|
---
|
|
|
|
## LanceDB Embedded {#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 |
|
|
|
|
For anything the community can't resolve, email
|
|
[support@lancedb.com](mailto:support@lancedb.com).
|
|
|
|
### What to include {#what-to-include}
|
|
|
|
A faster answer usually depends on the same handful of details, whether you
|
|
post in Discord or email:
|
|
|
|
| | |
|
|
| --- | --- |
|
|
| 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 |
|
|
|
|
## LanceDB Enterprise {#enterprise}
|
|
|
|
Talk to your account executive, file a support ticket, or reach the LanceDB
|
|
support and engineering team directly for dedicated assistance.
|