opteryx-upload
Python client SDK for the Opteryx Upload Service.
Install
pip install opteryx-upload
Usage
from opteryx_upload import UploadClient, Target, ConflictResolution
client = UploadClient(token="<jwt>") # or token=lambda: fetch_fresh_token()
session = client.create_session()
session.upload_file("findings.parquet")
session.upload_file("more_findings.csv") # auto-split into <30MB parts if needed
result = session.inspect()
if result.has_issues:
raise SystemExit(result.issues)
commit = session.commit(
Target(workspace="acme", collection="security", dataset="findings"),
snapshot_message="Initial load",
conflict_resolution=ConflictResolution.APPEND,
)
print(commit.table, commit.commit_id, commit.rows_written)
Or in one call:
client.upload_and_commit(
["findings.parquet"],
Target("acme", "security", "findings"),
snapshot_message="Initial load",
)
Authenticating with a Personal Access Token (PAT)
If you have a PAT (client_id + client_secret) instead of a ready-made JWT, use
PATAuthenticator to exchange it for a short-lived access token. It caches the
token and transparently re-authenticates before it expires, so you can pass it
straight through as token=:
from opteryx_upload import UploadClient, PATAuthenticator
auth = PATAuthenticator(client_id="<client_id>", client_secret="<pat_secret>")
client = UploadClient(token=auth)
This exchanges the PAT via POST {auth_url}/token with grant_type=client_credentials
(default auth_url is https://authenticate.opteryx.app), the same flow used by
the opteryx-sqlalchemy driver. If the API ever rejects a token as expired/invalid,
call auth.invalidate() and retry to force a fresh exchange.
Examples
Each UploadSession maps directly onto the service's REST flow: create a session,
stage one or more parts, inspect them, then commit. See the
service README for the underlying
HTTP API these calls wrap.
End-to-end: upload and commit a dataset
from opteryx_upload import UploadClient, Target, ConflictResolution
client = UploadClient(token="<jwt>")
session = client.create_session()
print(session.info.session_id, session.info.expires_at) # sessions expire after 6 hours
session.upload_file("findings.parquet")
session.upload_file("more_findings.parquet")
result = session.inspect()
print(result.rows_estimate, result.schema)
if result.has_issues:
for issue in result.issues:
print(f"part {issue.part}: {issue.issue}")
raise SystemExit("fix the reported issues before committing")
commit = session.commit(
Target(workspace="acme", collection="security", dataset="findings"),
snapshot_message="Initial load of findings",
conflict_resolution=ConflictResolution.FAIL, # default: error if the dataset already exists
)
print(f"committed {commit.rows_written} rows across {commit.files_created} files as {commit.commit_id}")
Choosing a conflict resolution strategy
ConflictResolution.FAIL(default) — reject the commit if the dataset already exists.ConflictResolution.APPEND— add the new rows to the existing dataset (schemas must match).ConflictResolution.OVERWRITE— replace the existing dataset's contents entirely.
session.commit(
Target("acme", "security", "findings"),
conflict_resolution=ConflictResolution.OVERWRITE,
)
Uploading many files, then deciding what to commit
Parts can be staged incrementally (e.g. from multiple upload jobs) before a single commit, and a bad part can be removed before it's committed:
session = client.create_session()
part_numbers = []
for path in ("2026-01.parquet", "2026-02.parquet", "2026-03.parquet"):
part_numbers += session.upload_file(path)
result = session.inspect()
if result.has_issues:
bad_part = result.issues[0].part
session.delete_part(bad_part)
result = session.inspect()
session.commit(Target("acme", "security", "findings"))
Handling errors
from opteryx_upload import (
UploadClient,
ConflictError,
SessionExpiredError,
UnprocessableEntityError,
)
client = UploadClient(token="<jwt>")
session = client.create_session()
try:
session.upload_file("findings.csv")
session.commit(Target("acme", "security", "findings"))
except UnprocessableEntityError as exc:
print(f"file rejected: {exc}")
except ConflictError as exc:
print(f"commit conflict, consider ConflictResolution.APPEND/OVERWRITE: {exc}")
except SessionExpiredError:
session = client.create_session() # start over with a fresh session
One-shot upload
For simple jobs where you just want to push files straight into a table:
client.upload_and_commit(
["findings.parquet"],
Target("acme", "security", "findings"),
snapshot_message="Initial load",
)
Authenticating with a PAT end-to-end
from opteryx_upload import UploadClient, PATAuthenticator, Target
client = UploadClient(
token=PATAuthenticator(client_id="acme-etl", client_secret="opt_XXXXXXXX_01"),
)
client.upload_and_commit(["findings.parquet"], Target("acme", "security", "findings"))
Notes
- Files are auto-typed from their extension (
.parquet,.csv,.ndjson/.jsonl). - CSV and NDJSON files larger than the part size limit are automatically split into multiple parts (CSV chunks repeat the header row). Parquet is a binary format and cannot be split this way — write multiple smaller parquet files and upload each as a separate part if a single export is too large.
- Errors map to typed exceptions (
AuthenticationError,SessionExpiredError,ConflictError,UnprocessableEntityError, etc.) so callers can catch specific failure modes instead of parsing HTTP status codes. tokenmay be a plain string or a zero-arg callable, so short-lived JWTs can be refreshed transparently between requests.
Development
pip install -e ".[dev]"
pytest tests/
Release files for opteryx-upload 0.2.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| opteryx_upload-0.2.1.tar.gz | 17.3 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| opteryx_upload-0.2.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 32.7 kB
Release files / opteryx_upload-0.2.1.tar.gz
| Download URL | opteryx_upload-0.2.1.tar.gz |
|---|---|
| Size | 17.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
136a9fb5127ff87ca268c56a45643ca86ffbe4e98de9d7b461ce0edc79addbd7
|
|
BLAKE2b-256 checksum How to use checksums |
1674e6b09a5c81b499660714adea9d5f895072a40142bda726a63a2ae9e64040
|
| 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 Aug 17, 2026.
Transparency logRelease files / opteryx_upload-0.2.1-py3-none-any.whl
| Download URL | opteryx_upload-0.2.1-py3-none-any.whl |
|---|---|
| Size | 15.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
cf623b8b69de73c4fde60ade2997a4d45c844e7f7ebfc9c173a1b80e671d4459
|
|
BLAKE2b-256 checksum How to use checksums |
9335690744e9a124e3c8c321cff2de1f4ca1de3eebb5a1ae5d76604dba6846b3
|
| 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 Aug 17, 2026.
Transparency log