Current release status: hold for the independently reproduced LargeList reader regression in https://github.com/lancedb/lancedb/pull/4712#discussion_r4409195229. All 54 CI checks passed at `a26e461b86728f7e7977f1c221af70a32033a144`; passing CI does not clear that compatibility finding. The Java artifact availability finding is fixed: the official Lance Maven mirror and Maven Central now serve the 14.0.2 POM and JAR (HTTP 200). [The rerun on the same candidate](https://github.com/lancedb/lancedb/actions/runs/40826169185/job/123300577435) downloaded the official stable artifact and passed all 37 Java tests with zero failures/errors/skips. The release remains blocked by the separate reader issue. Pin the LanceDB 0.41 release branch to the official Lance 14.0.2 packages. Keep the frozen product baseline at `45f987a29b6c12feb2b5fc613a6593e5f636a7ce` and the newer Lance dependency on main. All 15 Rust declarations use exact crates.io versions, Python uses the official stable wheel, and Java uses the stable Maven artifact. The vendored Lance Arrow and object_store Git overrides are removed. The LSM `BitmapAsBTree` change is limited to its test adapter and retains the physical-ID and query assertions. The Lance Arrow declaration remains inherited from the workspace. Validation: - The same source against official RC1 passed all 50 relevant PR checks, including 1,977 Rust core tests and the nullable-struct regression. - Stable source commit `40f15ed1b71b66950961b175829fdf17a763f108` differs from voted RC1 only by version substitutions in eight files. - `cargo fmt --all -- --check` and `cargo clippy --profile ci --features remote --tests --examples` passed against the official crates.io packages. - Locked Cargo metadata and normalized Cargo packaging passed; 995 unrelated Cargo lock entries were retained. - Six official PyPI wheel URLs/hashes are locked. Frozen environment installation, `lance` 14.0.2 import, and Ruff format/check passed. Unrelated UV packages and resolution markers are retained. - Full CI on the stable dependency commit is required before merge. Local Python SDK tests were not run because this validation environment has no installed LanceDB native extension; those tests run in PR CI. - Java checks run in CI; no local JDK is installed. Upstream release: https://github.com/lance-format/lance/releases/tag/v14.0.2 Remote materialized-view operations now use SQL and require matching server command support; older servers can reject describe/list operations. This known compatibility issue is outside the Lance patch scope and does not block this release, as agreed by the release manager. CI compatibility: derive the Lance checkout tag from an exact registry version when no Git tag is declared, and exercise local overrides for both crates.io and Git consumers. Both RC/stable tag readers and the exact stable downstream consumer metadata probe passed locally. This changes only the workflow; the 14.0.2 dependency/product code is unchanged. Release-hook correction: the dry run exposed Maven being set to `0.41.0-final.0`. Omit bump-my-version's optional `final` marker in the Java version hook so all SDKs publish as `0.41.0`. The actual hook passed beta.0, beta.17, final.0 and absent-prerelease probes; a fresh full stable dry run verifies Maven output before publication.
LanceDB Python SDK
A Python library for LanceDB.
Installation
pip install lancedb
If no wheel is published for your platform, pip builds lancedb from the source distribution. That build needs a Rust toolchain and protoc (the Protocol Buffers compiler) on your PATH, and can take a while.
Pre-Haswell x86_64 hosts: lancedb-compat
The default lancedb wheel targets x86-64-haswell (AVX2 + FMA + F16C) for full performance on modern hardware. Pre-Haswell hosts — Intel Sandy Bridge / Ivy Bridge / Westmere; AMD Bulldozer / Piledriver / Steamroller — don't have AVX2 and crash with Illegal instruction at import lancedb.
For those hosts, install the lancedb-compat package instead:
pip install lancedb-compat
Same Python API (import lancedb works as usual). The compat wheel is compiled at the x86-64-v2 baseline (Nehalem-class) and uses runtime SIMD dispatch in the embedded lance crate to pick the right kernel tier (scalar / AVX / AVX+FMA / AVX2+FMA / AVX-512) at load time, so it still goes fast on modern hardware while running cleanly on the pre-Haswell silicon. Use lance.simd_info() from Python to verify which tier was selected.
lancedb and lancedb-compat install to the same lancedb/ namespace and conflict at install time. Pick one. To switch, pip uninstall lancedb first, then pip install lancedb-compat (or vice-versa).
If you need a custom baseline (or lancedb-compat isn't yet published for your platform), build from source with the override:
RUSTFLAGS="-C target-cpu=x86-64-v2" maturin build --release
pip install ./target/wheels/lancedb-*.whl
Preview Releases
Stable releases are created about every 2 weeks. For the latest features and bug fixes, you can install the preview release. These releases receive the same level of testing as stable releases, but are not guaranteed to be available for more than 6 months after they are released. Once your application is stable, we recommend switching to stable releases.
pip install --pre --extra-index-url https://pypi.fury.io/lancedb/ lancedb
If you also need the optional lance Python API, install the pylance extra
and include the Lance preview index:
pip install --pre \
--extra-index-url https://pypi.fury.io/lancedb/ \
--extra-index-url https://pypi.fury.io/lance-format/ \
"lancedb[pylance]"
With uv, also select the best matching version across the indexes:
uv pip install --prerelease allow \
--index https://pypi.fury.io/lancedb/ \
--index https://pypi.fury.io/lance-format/ \
--index-strategy unsafe-best-match \
"lancedb[pylance]"
The LanceDB preview index contains old pylance releases; current Lance previews
are published to the lance-format index. By default, uv only considers versions
from the first index containing a package, which can select an old pylance or
backtrack to an older LanceDB release. unsafe-best-match searches all configured
indexes, like pip; use it only with indexes you trust. Install the extra rather
than an unconstrained pylance so LanceDB's minimum supported version is enforced.
Threading in CPU-limited containers
LanceDB uses separate pools for compute work and storage I/O. On a container with two visible CPUs, current releases intentionally use one compute worker by default; no manual configuration is needed. If every query logs an I/O core reservation warning on a two-CPU container, upgrade from LanceDB 0.21.1 or earlier.
The two commonly tuned environment variables control different resources:
LANCE_CPU_THREADSoverrides the number of compute workers. One worker is the appropriate setting for a two-CPU container when an explicit override is needed.LANCE_IO_THREADScontrols concurrent storage operations, not reserved CPU cores. Its default can be greater than the number of CPUs because I/O workers spend much of their time waiting for storage.
Keep the defaults unless measurements show that the workload benefits from an override. See the Lance threading model for the current defaults and tuning guidance.
Usage
Basic Example
import lancedb
db = lancedb.connect('<PATH_TO_LANCEDB_DATASET>')
table = db.open_table('my_table')
results = table.search([0.1, 0.3]).limit(20).to_list()
print(results)
Development
See CONTRIBUTING.md for information on how to contribute to LanceDB.
Opening SQL blob descriptors
A SQL blob_descriptor(video) result keeps the Blob V2 storage metadata and a
source struct containing its table URI, version, commit timestamp, branch,
column and row identity. This example uses a remote SQL connection whose SQL
service produces those source-bearing descriptors. Open the reference on the
source table to read incrementally:
rows = db.execute_query("""
SELECT f.timestamp, blob_descriptor(v.video) AS video
FROM videos v JOIN frames f ON v.id = f.video_id
""").read_all()
videos = db.open_table("videos")
for row in rows.to_pylist():
if row["video"] is not None:
with videos.open_blob_file(row["video"]) as video:
frame = extract_frame(video, row["timestamp"])
open_blob_file accepts the dictionary or an Arrow struct scalar directly. It
keeps the query's version and branch without changing the table handle's checkout.
Payload bytes load on reads. An external blob with an unspecified size may need a
metadata-only HEAD request to open.
videos.open_blob_files(rows["video"]) returns an iterator over the same handles,
preserving order, duplicates and nulls (None). It accepts Arrow arrays/chunked
arrays or another iterable and opens each handle as iteration advances. Close each
non-null handle after use. Async tables offer await videos.open_blob_file(...)
and async for video in videos.open_blob_files(...).
for video in videos.open_blob_files(rows["video"]):
if video is not None:
with video:
header = video.read(4096)
To extract a frame while retaining each row's timestamp, iterate over the handles and rows together:
for row, video in zip(rows.to_pylist(), videos.open_blob_files(rows["video"])):
if video is not None:
with video:
frame = extract_frame(video, row["timestamp"])