kumo_relational_engine
The Kumo Relational driver for the kumo-relational-client client.
This distribution provides the heavy, client-side machinery a Kumo Relational prediction
needs before a request reaches a NIM: the relational Graph/Table abstractions,
the neighbor samplers (local native relationallib, plus DuckDB / SQLite / Snowflake /
Databricks / PostgreSQL backends), the PQL parser, and the HTTP client that talks to a Universal
TFM NIM.
It is imported as kumo_relational_engine and is normally installed transitively via the client's
relational extra rather than on its own:
pip install kumo-relational-client[relational] # pulls the kumo_relational_engine driver
It can also be installed on its own, for the graph, sampler and PQL machinery.
Predicting is not available that way: the engine's entry points refuse a direct
call, so a prediction has to go through kumo-relational-client.
pip install kumo-relational-engine
# optional data backends:
pip install "kumo-relational-engine[duckdb]" # or [sqlite] / [snowflake] / [databricks] / [postgres]
# optional features:
pip install "kumo-relational-engine[explain]" # natural-language explanation summaries
pip install "kumo-relational-engine[relbench]" # Graph.from_relbench() dataset loading
pip install "kumo-relational-engine[codegen]" # regenerate the TFM API client (see scripts/)
Graph.from_postgres() reads existing PostgreSQL tables:
import psycopg
from kumo_relational_client import relational
connection = psycopg.connect(
host=host,
dbname=database,
user=user,
password=credential,
sslmode='require',
)
graph = relational.Graph.from_postgres(connection, schema='public')
schema is the table namespace; omit it to use current_schema() (public is
the usual default). connection may instead be a PostgreSQL URI/libpq string
or a dictionary of psycopg arguments; if omitted, psycopg uses PG* environment
variables. See postgres.py. Lakebase uses this same
API through its PostgreSQL endpoint with TLS and either an OAuth token or an
enabled native Postgres password. It reads existing tables directly—without
Unity Catalog registration, copying data, or DDL.
Temporal sampling returns at most the requested latest N rows at or before each
anchor, ordered by time descending then primary key ascending. For large fact
tables, an index on (foreign_key, time_column DESC, primary_key) improves this
pushed-down query; the SDK never creates indexes or modifies source tables.
Release wheels are built for CPython 3.10, 3.11, 3.12 and 3.13
(manylinux_2_28 x86-64), plus CPython 3.12 on Linux ARM64. No source
distribution is published.
Application code should import the client's neutral surface, not this package directly:
from kumo_relational_client import RelationalClient, relational
graph = relational.Graph.from_data({'users': df1, 'items': df2, 'orders': df3})
with RelationalClient(url='http://localhost:8000') as client:
result = client.relational(graph).predict(
'PREDICT SUM(orders.price, 0, 30, days) FOR items.item_id=1'
)
Local development
pip install -e ".[test,databricks]"
pytest tests -m "not live_nim"
The live-NIM suite (scripts/run_rfm_nim_live_tests.sh --full) includes durable,
ticket-free rejection regressions for fixed NIM defects; every rejection probe is
followed by a known-good prediction to detect service degradation.
The native neighbor sampler (kumo_relational_engine.relationallib) is built from
src/kumo_relational_engine/csrc/neighbor_sampler.cpp via CMake/scikit-build-core. Set
WITH_RELATIONALLIB=0 to skip the native build for a pure-Python editable install.
Metadata
Release files for kumo-relational-engine 1.0.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distributions (wheels)
| File | Reset | |||
|---|---|---|---|---|
| kumo_relational_engine-1.0.0-cp313-cp313-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl | CPython 3.13 | CPython 3.13 | Linux glibc 2.28+ x86-64, Linux glibc 2.27+ x86-64 | Details |
| kumo_relational_engine-1.0.0-cp312-cp312-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl | CPython 3.12 | CPython 3.12 | Linux glibc 2.28+ x86-64, Linux glibc 2.27+ x86-64 | Details |
| kumo_relational_engine-1.0.0-cp312-cp312-manylinux_2_26_aarch64.manylinux_2_28_aarch64.whl | CPython 3.12 | CPython 3.12 | Linux glibc 2.26+ ARM64, Linux glibc 2.28+ ARM64 | Details |
| kumo_relational_engine-1.0.0-cp311-cp311-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl | CPython 3.11 | CPython 3.11 | Linux glibc 2.28+ x86-64, Linux glibc 2.27+ x86-64 | Details |
| kumo_relational_engine-1.0.0-cp310-cp310-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl | CPython 3.10 | CPython 3.10 | Linux glibc 2.28+ x86-64, Linux glibc 2.27+ x86-64 | Details |
Total release size: 7.0 MB
Release files / kumo_relational_engine-1.0.0-cp313-cp313-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl
| Download URL | kumo_relational_engine-1.0.0-cp313-cp313-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl |
|---|---|
| Size | 1.4 MB |
| Tags | CPython 3.13 Linux glibc 2.27+ x86-64 Linux glibc 2.28+ x86-64 |
|
SHA-256 checksum How to use checksums |
29f7cc566094bf94b6f984a9958679ecd9fb0363bd2a286df018482a2c379f3b
|
|
BLAKE2b-256 checksum How to use checksums |
970c5e99ae88665db28863150ebc73c430cb9e8f2068abe41125d51bfc9ba753
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 8, 2026.
Transparency logRelease files / kumo_relational_engine-1.0.0-cp312-cp312-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl
| Download URL | kumo_relational_engine-1.0.0-cp312-cp312-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl |
|---|---|
| Size | 1.4 MB |
| Tags | CPython 3.12 Linux glibc 2.27+ x86-64 Linux glibc 2.28+ x86-64 |
|
SHA-256 checksum How to use checksums |
aeedc82f1c872537dd49d265cffa8f56a692c00d3b269fd21b4aa741fcfcedd1
|
|
BLAKE2b-256 checksum How to use checksums |
4fa422fe8c6445881d55dfcf8d10f9f334ccf8b761e963f7685d0e33770558b1
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 8, 2026.
Transparency logRelease files / kumo_relational_engine-1.0.0-cp312-cp312-manylinux_2_26_aarch64.manylinux_2_28_aarch64.whl
| Download URL | kumo_relational_engine-1.0.0-cp312-cp312-manylinux_2_26_aarch64.manylinux_2_28_aarch64.whl |
|---|---|
| Size | 1.4 MB |
| Tags | CPython 3.12 Linux glibc 2.26+ ARM64 Linux glibc 2.28+ ARM64 |
|
SHA-256 checksum How to use checksums |
10e38cb51485cf91ee088a4d600f233ded7ef34bc582333b64b6117371224819
|
|
BLAKE2b-256 checksum How to use checksums |
5f1ee77274142a0a6ffdd4b8b321d508cef37e705238b4eee2340dfda2840861
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 8, 2026.
Transparency logRelease files / kumo_relational_engine-1.0.0-cp311-cp311-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl
| Download URL | kumo_relational_engine-1.0.0-cp311-cp311-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl |
|---|---|
| Size | 1.4 MB |
| Tags | CPython 3.11 Linux glibc 2.27+ x86-64 Linux glibc 2.28+ x86-64 |
|
SHA-256 checksum How to use checksums |
85925091d4f3ac37bd73d652c6b40787e7e1c3026cb2b9a0238bf58ee0bea30f
|
|
BLAKE2b-256 checksum How to use checksums |
d48e2e16b615b3381e1db8a9865b1892b3fc2db60b572b26305171d3920dcf70
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 8, 2026.
Transparency logRelease files / kumo_relational_engine-1.0.0-cp310-cp310-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl
| Download URL | kumo_relational_engine-1.0.0-cp310-cp310-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl |
|---|---|
| Size | 1.4 MB |
| Tags | CPython 3.10 Linux glibc 2.27+ x86-64 Linux glibc 2.28+ x86-64 |
|
SHA-256 checksum How to use checksums |
35ac185a40af539807bb64c611734559ba65929b725654393bdbac5d74ac8f2d
|
|
BLAKE2b-256 checksum How to use checksums |
eee0df589c6548675677f2d39b093041006a37d8537b26c4478716ddf3552bd7
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 8, 2026.
Transparency logSecurity for kumo-relational-engine 1.0.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
All 5 files in this release have been uploaded with provenance metadata.
Attestation for kumo_relational_engine-1.0.0-cp313-cp313-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 8, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.