lance-format

Solid

Deep reference for Lance v12 columnar format, its Rust crates, and pylance - file encodings, table format, indexes, schema evolution, time travel. Use when building on the Lance crates or reading .lance datasets, not the LanceDB product.

Code & Development 36 stars 1 forks Updated today MIT

Install

View on GitHub

Quality Score: 85/100

Stars 20%
52
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
80
License 10%
100
Description 5%
100

Skill Content

# Lance v12 reference Lance is an open columnar format for multimodal AI - "a columnar data format that is 100x faster than Parquet for random access." It is not one format but a stack of interoperating specs: a **file format**, a **table format**, **index formats**, **catalog specs**, and a **namespace client spec**. The Rust workspace at `lance-format/lance` implements all of them plus Python (`pylance`) and Java bindings. This skill tracks **`v12.0.0-beta.15`** (the `lance-format/lance` git tag), the current development frontier; **`v11.0.0`** is the stable pin. Pin against tags, not `main` - Lance ships beta tags every few days and `next`-format encodings can change. Version landscape below. Three layers of reference, load what the task needs: - **The deep reference** - any concrete schema, parameter, proto, or constraint. Split by topic: | File in `references/` | Covers | Sections | |------|--------|----------| | `format-file.md` | What Lance is, the 26 crates, file format, data types | 1-4 | | `format-table.md` | Dataset layout, manifests, fragments, schema evolution, versioning/tags/branches, row IDs, transactions + OCC, MemWAL | 5-10 | | `indexes.md` | Vector / scalar / FTS / geo indexes, distributed builds | 11-12 | | `ops.md` | Object store, capability matrix, source map | 13, 15, 16 | | `changelog-v7-v12.md` | The full v7 -> v12 delta | 14 | Cross-references written as "section N" resolve through `references/lance-reference.md`. - `references/...

Details

Author
tenequm
Repository
tenequm/skills
Created
10 months ago
Last Updated
today
Language
Python
License
MIT

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Listed

vllm-deployment

Use this skill when authoring, reviewing, or fixing a vLLM Kubernetes manifest, Docker/Podman pod, or OpenShift ServingRuntime — even when the user does not say "vllm". Triggers on: lab cluster performance practices, cache mount + survival across pod restarts (/root/.cache, VLLM_CACHE_ROOT, TORCHINDUCTOR_CACHE_DIR, TRITON_CACHE_DIR, "do we have caches saved"), HF_TOKEN secret in pod env, liveness + readiness probe tuning (initialDelaySeconds, failureThreshold, "pod takes 12 min to boot"), serve_args review, --enforce-eager rationale, MoE deployment ("ep2 dp2", --enable-expert-parallel, expert-parallel sizing), TP/PP sizing, ConfigMap parser-plugin mount, image tag selection, cold-boot reduction, multi-node LWS + Ray, control planes (llm-d, production-stack, AIBrix, NVIDIA Dynamo, KServe), KEDA autoscaling, GAIE routing, disaggregated prefill/decode (Nixl/Mooncake/LMCache/MORI-IO), RHAIIS on OpenShift (SCC, arbitrary UID, Routes 60s, ModelCar, air-gapped). Lead with operator intent, not vendor names.

5 Updated 1 weeks ago
air-gapped
AI & Automation Listed

rails-reference

Worked code examples for this project's Rails layer conventions — models, ActiveRecord queries, database/migrations, controllers & routing, business logic (services/forms/ policies), background jobs, caching & storage, and security. CONSULT when implementing or reviewing a Rails layer and you need the idiomatic example (model structure, N+1 fixes, service patterns, thin controllers, idempotent jobs, caching, strong params/SQL safety). Reference loaded on demand — the always-apply rules live in the matching `rails-*` rules.

2 Updated 1 weeks ago
mik2win
AI & Automation Listed

stack-reference

Full tech stack reference and dev command cheatsheet. Load when you need to look up exact package names, commands, or project paths.

8 Updated yesterday
ek33450505