mirror of
https://github.com/lancedb/lancedb.git
synced 2026-11-02 08:46:52 +00:00
Jack Ye
75eefedc4b
Dropping a view unbinds its name and leaves the definition dataset to a cleanup job, so the two are separate events a caller may want to wait on. `drop_view_async` returns the job, the same shape `drop_materialized_view_async` and `drop_function_async` already use: a 202 carries the job id, and a 200 -- nothing bound to the name -- yields an already-finished job. `drop_view` waits on that job before returning, so a caller that does not want to think about cleanup gets the stronger guarantee: when it returns, the definition really is deleted. That differs from `drop_materialized_view` and `drop_function`, which return as soon as the name is unbound; the view API is the newer one and this is the semantic worth having.
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.