Skip to content

Make sure people know they'll have to set up a cluster #195

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
dantasse merged 2 commits into from
Mar 23, 2026
Merged

Make sure people know they'll have to set up a cluster #195

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
2c7ed0c
Make sure people know they'll have to set up a cluster
dantasse Mar 23, 2026
97d5bbe
Also update contexts
dantasse Mar 23, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 4 additions & 1 deletion docs/geneva/index.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -37,6 +37,9 @@ as columns in a Lance dataset. Adding a feature is straightforward:
Register the UDF as a virtual column using `Table.add_columns()`.
</Step>
<Step>
(Optional) Configure where the UDF will run: locally, on a Ray cluster, or on a Kubernetes cluster with KubeRay (see [Contexts](/geneva/jobs/contexts)).
</Step>
<Step>
Trigger a `backfill` operation (see [Backfilling](/geneva/jobs/backfilling/)).
</Step>
</Steps>
Expand All @@ -52,4 +55,4 @@ Visit the following pages to learn more about featuring engineering in LanceDB E
- **Overview**: [What is Feature Engineering?](/geneva/overview/)
- **UDFs**: [Using UDFs](/geneva/udfs/udfs) · [Blob helpers](/geneva/udfs/blobs/) · [Error handling](/geneva/udfs/error_handling) · [Advanced configuration](/geneva/udfs/advanced-configuration)
- **Jobs**: [Backfilling](/geneva/jobs/backfilling/) · [Startup optimizations](/geneva/jobs/startup/) · [Materialized views](/geneva/jobs/materialized-views/) · [Execution contexts](/geneva/jobs/contexts/) · [Geneva console](/geneva/jobs/console) · [Performance](/geneva/jobs/performance/)
- **Deployment**: [Deployment overview](/geneva/deployment/) · [Helm deployment](/geneva/deployment/helm/) · [Troubleshooting](/geneva/deployment/troubleshooting/)
- **Deployment**: [Deployment overview](/geneva/deployment/) · [Helm deployment](/geneva/deployment/helm/) · [Troubleshooting](/geneva/deployment/troubleshooting/)
6 changes: 2 additions & 4 deletions docs/geneva/jobs/contexts.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,17 +1,15 @@
---
title: Execution Contexts
sidebarTitle: Contexts
description: Learn how Geneva automatically packages and deploys your Python execution environment to worker nodes for distributed execution.
description: Learn how to set up your cluster for distributed execution.
icon: circle-nodes
---

<Note>
The APIs on this page require Geneva **v0.10.0** or later.
</Note>

Geneva automatically packages and deploys your Python execution environment to its worker nodes. This ensures that distributed execution occurs in the same environment and dependencies as your prototype.

We currently support one processing backend: **Ray**. There are 3 ways to connect to a Ray cluster:
Geneva currently supports one processing backend: **Ray**. There are 3 ways to connect to a Ray cluster:

1. Local Ray
2. KubeRay: create a cluster on demand in your Kubernetes cluster.
Expand Down
Loading