Upgrade the Rust Lance family from beta.18 to the published v15.0.0-beta.21 tag, and align Python test wheels and Java artifacts. This includes the explicit-empty-segment FTS fix in lance-format/lance#11063 needed by lancedb/sophon#10314. Enable Windows Git long paths so Cargo can check out Lance fixtures in the Rust, NPM and Python wheel builds. Beta.21 also contains lance-format/lance#9858: new NGram, RTree and MinHash LSH indexes use row addresses. Legacy row-ID segments remain readable, but index maintenance on stable-row-ID tables can require a rebuild. The NGram documentation now explains the consolidation requirement; NGram/RTree tables without stable row IDs retain their earlier format. The Python lock revision and unrelated dependency entries are unchanged. Validation: - The official Lance release and internal mirror match 80bc45a195279befdec42853dac8d15a37e0504d. The seven official Fury wheels and Maven POM/JAR were verified. - Exact executable/dependency state7846a15ecompleted the full Rust, Python, Node, Java and CLI CI, including platform builds and package publication dry runs. Xuanwo approved that head; Gatekeeper recommended approve with a non-blocking qualification risk. - Follow-upa289cb2conly adds the requested seven-line NGram upgrade note. Static whitespace checks passed; new-head CI is running. No local correctness tests or test builds were run by this task owner. - Broader IVF/encoding/Blob/cache workload performance and the beta.21 Sophon composition remain separately qualified. Earlier Blob cancellation and DynamoDB failures on #4967 are retained in their original evidence; this PR does not count those historical failures as fixed. Current-head CI, full feedback and required review still gate merge. SDK publication is a separate action. Sophon adoption follows a published SDK release and mirror through its own dependency PR; its distributed performance acceptance remains in #10314.
LanceDB Java Enterprise Client
Installation
Stable releases of com.lancedb:lancedb-core are published to Maven Central.
Beta releases are published to https://maven.fury.io/lancedb/ instead. They
depend on Lance beta releases, which are published to https://maven.lance.org.
To use a beta, add both repositories alongside Maven Central:
<repositories>
<repository>
<id>lancedb</id>
<url>https://maven.fury.io/lancedb/</url>
</repository>
<repository>
<id>lance</id>
<url>https://maven.lance.org</url>
</repository>
</repositories>
For Gradle:
repositories {
mavenCentral()
maven { url = uri("https://maven.fury.io/lancedb/") }
maven { url = uri("https://maven.lance.org") }
}
Use an explicit version, including the full -beta.N suffix. Beta versions are
Maven releases, not SNAPSHOT versions.
Configuration and Initialization
LanceDB Cloud (legacy)
For LanceDB Cloud, the legacy hosted service, 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 LanceDB 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();
RTE write path
Most table operations reach LanceDB through the LanceNamespace above, which is
generated from the Lance Namespace specification. The RTE LSM routes are not part
of that specification, so they are issued through a separate client:
import com.lancedb.LanceDbRestClient;
import com.lancedb.LanceDbTableRTE;
import com.lancedb.RTEWriteSpec;
LanceDbRestClient client = LanceDbNamespaceClientBuilder.newBuilder()
.apiKey("your_lancedb_cloud_api_key")
.database("your_database_name")
.buildRestClient();
LanceDbTableRTE rte = new LanceDbTableRTE(client, "my_table");
// Route future merge_insert upserts through the RTE, hash-bucketed by `id`.
rte.enableRTE(RTEWriteSpec.bucket("id", 16));
// ... merge_insert traffic ...
// Converge the fresh tier into the base table.
rte.checkpointRTE();
// Inspect live per-table-shard state.
rte.getRTEStats().ifPresent(stats -> stats.tableShards().forEach(tableShard ->
System.out.println(tableShard.shardId() + ": " + tableShard.sstables().size() + " SSTables")));
client.close();
maintainedIndexes is tri-state, and the null default is the opposite of what a Java
reader usually expects:
| Value | Meaning |
|---|---|
| unset (null) | Maintain every index the table has, including ones created later |
Collections.emptyList() |
Maintain none |
Arrays.asList("id_idx") |
Maintain exactly those |
Development
The parent POM includes https://maven.lance.org to resolve Lance beta and RC
dependencies. Use an explicit lance-core.version; numbered beta and RC versions
are Maven releases, not snapshots. Maven Central remains available for stable
and historical versions, as well as other dependencies.
Build:
./mvnw install -pl lancedb-core -am
Run tests:
./mvnw test -pl lancedb-core