mirror of
https://github.com/lancedb/lancedb.git
synced 2026-05-14 02:20:40 +00:00
Re-targets the v0.28 release branch at lance 6.0.0 stable. Because lance 6.0.0 directly uses object_store 0.12 while main has moved to object_store 0.13, the change also reverts the object_store 0.13 port from #3348: * workspace `object_store` pin back to 0.12 * `rust/lancedb` aws feature no longer enables `object_store/aws` * `MirroringObjectStore` and `IoTrackingStore` restored to the 0.12 trait shape (overrides for `copy`, `delete`, `head`, etc. — no `copy_opts`/`rename_opts`/new `delete_stream` signature) * `listing.rs`: `Path::clone().join(...)` → `Path::child(...)` * `python/pyproject.toml`: `pylance>=6.0.0` (stable) * `java/pom.xml`: `lance-core` 6.0.0 Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
LanceDB Java Enterprise Client
Configuration and Initialization
LanceDB Cloud
For LanceDB Cloud, use the simplified builder API:
import com.lancedb.LanceDbNamespaceClientBuilder;
import org.lance.namespace.LanceNamespace;
// If your DB url is db://example-db, then your database here is example-db
LanceNamespace namespaceClient = LanceDbNamespaceClientBuilder.newBuilder()
.apiKey("your_lancedb_cloud_api_key")
.database("your_database_name")
.build();
LanceDB Enterprise
For Enterprise deployments, use your custom endpoint:
LanceNamespace namespaceClient = LanceDbNamespaceClientBuilder.newBuilder()
.apiKey("your_lancedb_enterprise_api_key")
.database("your_database_name")
.endpoint("<your_enterprise_endpoint>")
.build();
Development
Build:
./mvnw install -pl lancedb-core -am
Run tests:
./mvnw test -pl lancedb-core