mirror of
https://github.com/lancedb/lancedb.git
synced 2026-10-13 15:22:30 +00:00
Brendan Clement
e20664740f
The two Function pages declare `launch: functions`, and every other page marks what it says about Functions, so the assembled site leaves them out until the launch. Before it, the pages that offered Functions for Python work point Enterprise readers at Geneva instead. The SQL Function example now uses Arrow type names, which the server requires, and states the 3.12 default for `python_version`.
30 lines
1.1 KiB
Plaintext
30 lines
1.1 KiB
Plaintext
---
|
|
title: "LanceDB Enterprise"
|
|
sidebarTitle: "Overview"
|
|
description: "What a deployment adds over embedded LanceDB."
|
|
icon: building
|
|
keywords: ["enterprise", "deployment", "cluster"]
|
|
---
|
|
|
|
<Badge color="red">Enterprise</Badge>
|
|
|
|
This page describes a LanceDB Enterprise capability. The embedded form
|
|
of LanceDB has no server to provide it -- see
|
|
[Architecture](/architecture) for what differs between the two.
|
|
|
|
LanceDB Enterprise runs the lakehouse as a service: a control plane for
|
|
configuration, identity and policy; a data plane serving reads and writes; and
|
|
indexers building indexes and compacting outside the request path.
|
|
|
|
What it adds over the embedded form:
|
|
|
|
| | |
|
|
| --- | --- |
|
|
| [SQL](/sql) | an Arrow Flight SQL endpoint |
|
|
| [Functions](/management/function) {/* if functions launched */} | Python running on workers |
|
|
| [Jobs](/basics/jobs) | server-side work with ids, status and events |
|
|
| [Authorization](/governance/authorization) | per-object grants |
|
|
| Scale | a cluster rather than your process |
|
|
|
|
See [Architecture](/architecture) for the two shapes side by side.
|