mirror of
https://github.com/lancedb/lancedb.git
synced 2026-11-14 14:46:53 +00:00
Three cleanups to the LsmWriteSpec surface, all removing something: `with_no_maintained_indexes` is gone. `with_maintained_indexes` now takes `impl Into<Option<Vec<String>>>`, so `None` asks for every supported index, a list pins an exact set, and an empty list maintains none — one method covering what two did, and the argument reads the same as the field it sets. `IndexConfig::is_memwal_maintainable` is gone. What a memtable can build is lance's to say, and lance already says it via `is_maintainable_index_type`; mirroring that onto a lancedb type only added a place for the two to drift. `resolve_maintained_indexes` is now public and takes `&[IndexConfig]` rather than a table. It was already the whole of the resolution rules — infer from the committed set, or validate a named one — and a server installing specs on a caller's behalf needs exactly those rules. Sharing it means sophon no longer keeps a second copy that could disagree about what an absent list means, and the error now names the table's indexes so a rejected call says what was actually available. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
LanceDB JavaScript SDK
A JavaScript library for LanceDB.
Installation
npm install @lancedb/lancedb
This will download the appropriate native library for your platform. We currently support:
- Linux (x86_64 and aarch64 on glibc and musl)
- MacOS (Intel and ARM/M1/M2)
- Windows (x86_64 and aarch64)
Usage
Basic Example
import * as lancedb from "@lancedb/lancedb";
const db = await lancedb.connect("data/sample-lancedb");
const table = await db.createTable("my_table", [
{ id: 1, vector: [0.1, 1.0], item: "foo", price: 10.0 },
{ id: 2, vector: [3.9, 0.5], item: "bar", price: 20.0 },
]);
const results = await table.vectorSearch([0.1, 0.3]).limit(20).toArray();
console.log(results);
The quickstart contains more complete examples.
Development
See CONTRIBUTING.md for information on how to contribute to LanceDB.