Files
lancedb/docs/web/tutorials/index.mdx
T
Jack Ye 70c10e4aa4 docs: own every page path, and port the upstream changes
lancedb now holds a page at every path the site publishes, including the twelve
Enterprise ones. Those are real open-source pages -- what the capability is, and
what the embedded form does instead -- rather than blank placeholders, so the
open-source site is complete on its own. sophon becomes an overlay whose page
replaces the one at the same path, which means navigation lives in one place and
the two repositories only have to agree on a path.

That removes the whole class of problem where a page could only be reached from
one of the two trees. The open-source site went from twenty-four dangling
Enterprise links to one, and that one points at the dataset pages the build
repository owns.

Ports four changes that landed on the docs repository after this branch left it:

  #344  indexing and quantization rewritten
  #354  LeRobot native reader
  #361  training/index renamed to training/data-loading and rewritten
  #362  distance metric mismatch falls back to a brute-force scan

None applied as patches, because these files were merged or split here --
quantization into the vector index page, multi-vector into vector search,
performance into four pages. Each was ported by taking the upstream page and
re-applying the restructure on top, which also picked up a correction that would
otherwise have been lost: the stricter brute-force threshold for multi-vector
columns is a Cloud limit, not an Enterprise one.

The upstream LeRobot page linked to a Geneva page that no longer exists; it now
points at the feature-engineering pages that replaced it.
2026-09-25 15:19:54 -07:00

43 lines
1.9 KiB
Plaintext

---
title: "Use cases"
sidebarTitle: "Overview"
description: "Worked examples of building with LanceDB, by what you are building."
---
Every example is one page in the sidebar, grouped by what it builds. The
documentation explains how a feature works; these show it doing something.
Examples marked as notebooks live in the
[vectordb-recipes](https://github.com/lancedb/vectordb-recipes) repository and
are runnable in Colab; the rest are written up here.
## Where to start {#start}
<CardGroup cols={2}>
<Card title="Search" icon="magnifying-glass" href="/tutorials/search/hybrid-search-beir">
Vector, multi-vector, hybrid and full-text retrieval.
</Card>
<Card title="RAG" icon="robot" href="/tutorials/agents/contextual-rag">
Retrieval-augmented generation and agent applications.
</Card>
<Card title="Feature engineering" icon="wand-magic-sparkles" href="/tutorials/feature-engineering/feature-engineering-101">
Deriving columns, materialized views, experimenting on branches.
</Card>
<Card title="Training" icon="graduation-cap" href="/training/object-detection">
Curating data and training models directly on a table.
</Card>
</CardGroup>
## The features these use {#read-the-docs}
| Feature | What it covers |
|:--------|:------------|
| [Vector search](/search/vector-search) | Similarity search, distance metrics, and tuning it. |
| [Full-text search](/search/full-text-search) | Keyword search over text columns. |
| [Hybrid search](/search/hybrid-search) | Keyword and vector search combined. |
| [Multi-vector search](/search/vector-search) | Several embeddings per document. |
| [Reranking](/reranking) | Reordering results to improve the top-k. |
| [Feature engineering](/feature-engineering) | Deriving columns and tables from data already stored. |
| [Materialized views](/management/materialized-view) | A table defined by a query, refreshed incrementally. |
| [Training](/training/data-loading) | Reading a table into a data loader. |