mirror of
https://github.com/lancedb/lancedb.git
synced 2026-11-13 22:26:53 +00:00
Brendan ClementandClaude Opus 5.5
dcddd541c8
## Summary Changes links to home page sections from `/#<anchor>` to `/index#<anchor>`. The docs site's Assemble CI fails `mint broken-links --check-anchors` on every `/#architecture` link since #4732 moved the Architecture page onto the home page. The anchor exists; Mint 4.2.888's checker can't resolve any anchor on the root page `/`, but resolves `/index#…`. `docs.lancedb.com/index` serves the home page, so readers land in the same place. Verified by assembling the site with this change and the matching Enterprise docs change: `mint validate` passes and `mint broken-links --check-anchors --check-redirects` finds no broken links. The `docs.json` redirects keep `/#architecture`, which the checker accepts. 🤖 Generated with [Claude Code](https://claude.com/claude-code) --------- Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
46 lines
1.8 KiB
Plaintext
46 lines
1.8 KiB
Plaintext
---
|
|
title: "Lance format"
|
|
sidebarTitle: "Lance Format"
|
|
description: "The open format for multimodal data behind LanceDB."
|
|
icon: "/static/assets/logo/lance-logo-gray.png"
|
|
keywords: ["lance", "format", "multimodal", "versioning", "column evolution"]
|
|
---
|
|
|
|
## Lance format overview {#standard}
|
|
|
|
[Lance](https://lance.org/) is an open-source, columnar format designed for
|
|
multimodal AI. It defines how data is stored and organized into versioned tables.
|
|
|
|
<span id="embedded" />
|
|
<span id="enterprise" />
|
|
|
|
LanceDB Embedded and LanceDB Enterprise both use Lance as their storage foundation.
|
|
The format is developed as an independent open-source project, with its own
|
|
specification and tools.
|
|
|
|
## Multimodal data {#storage}
|
|
|
|
A Lance table can hold images, video, audio, text, embeddings and structured
|
|
metadata together. For example, a video dataset can keep each clip alongside
|
|
its caption, labels and embeddings, so applications can search and work with
|
|
those fields together.
|
|
|
|
## Data access, versioning and column updates {#capabilities}
|
|
|
|
- **Efficient data access.** Read individual rows for retrieval and training,
|
|
or scan columns for analytics.
|
|
- **Versioned data.** Read an earlier table version to reproduce an experiment
|
|
or inspect previous results, while that version is retained.
|
|
- **Independent column updates.** Add embeddings or other derived features
|
|
without rewriting the existing image, video or text columns.
|
|
|
|
## Learn more {#next}
|
|
|
|
<span id="versioning" />
|
|
<span id="evolution" />
|
|
|
|
- [Lance format specification](https://lance.org/format): how the format works.
|
|
- [Table versioning](/management/table#versioning): read and manage table versions.
|
|
- [Computed columns](/feature-engineering/add-computed-column): add derived features to your data.
|
|
- [Architecture](/index#architecture): how LanceDB Embedded and Enterprise build on Lance.
|