Skip to main content
Connect to your LanceDB Enterprise deployment, define a UDF, and run a distributed backfill — all from a notebook or a script. No cluster setup required.

Installation

Geneva is published on PyPI. Install the latest stable release with uv (recommended) or pip. Newer pre-release builds with the latest features are also available on LanceDB’s Fury indexes — see Pre-release builds below.

Prerequisites

  • Python 3.10+
  • uv (recommended) or pip

Install the latest stable release

Verify

Pre-release builds

To pick up the newest features ahead of a stable release, install a pre-release from LanceDB’s Fury indexes. Geneva and its dependencies are published across two indexes:
The --index-strategy unsafe-best-match flag is required with uv. By default, uv only considers package versions from the first index that lists a given package (PyPI). Since geneva and pylance also appear on PyPI, this flag tells uv to pick the best match across all indexes.

Quickstart

Get the database URI, HTTPS endpoint and API key from your LanceDB Enterprise administrator, then replace the placeholders in the example. In application code, load credentials from environment variables or a secrets manager.

Auto-backfill

With auto_backfill=True, LanceDB Enterprise recomputes the column for you whenever the data or the UDF version changes — no explicit backfill() call needed (see Backfilling).

Materialized views and chunkers

A materialized view applies UDFs over a query and refreshes incrementally. A chunker view expands each source row into many rows (1:N) — useful for splitting documents, videos, or images.

Connecting to object storage or a local filesystem

Geneva can also run directly against cloud object storage or a local path. In this mode, jobs run on a distributed execution context you provide.