continuo-validation-trino
Trino warehouse adapter for the continuo
validation runner. Implements continuo_validation_contract.port.WarehouseAdapter;
continuo's harness discovers it through the continuo_validation.adapters entry point.
Trino's namespace is catalog.schema. The catalog comes from TRINO_CATALOG and every
statement is fully qualified, so continuo passes a bare candidate schema name and never
needs to know about catalogs.
Connection env
| Env | Required | Default | Purpose |
|---|---|---|---|
TRINO_HOST |
yes | — | Coordinator host |
TRINO_CATALOG |
yes | — | Catalog holding candidate schemas (e.g. iceberg) |
TRINO_PORT |
no | 8080 |
Coordinator port |
TRINO_USER |
no | continuo |
Trino user |
TRINO_HTTP_SCHEME |
no | http |
http or https |
TRINO_PASSWORD |
no | unset | Basic auth; requires TRINO_HTTP_SCHEME=https |
The catalog must be backed by a connector that supports schema and table creation
and DROP SCHEMA ... CASCADE (Iceberg and Hive do). The library is tested live against Iceberg (REST catalog + S3).
1 maintainer
Metadata
1 maintainer
Release files for continuo-validation-trino 0.1.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 | |
|---|---|---|---|
| continuo_validation_trino-0.1.1.tar.gz | 5.6 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| continuo_validation_trino-0.1.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 10.1 kB
Release files / continuo_validation_trino-0.1.1.tar.gz
| Download URL | continuo_validation_trino-0.1.1.tar.gz |
|---|---|
| Size | 5.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
05b0c40a701a8822db3420a8aa0c7622b2da62242ec2f54d44f29209650d92b6
|
|
BLAKE2b-256 checksum How to use checksums |
fa51876396e95e5691e56f166df5a00bb91d46d2aed842f67ee00edea9142e75
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.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 Jul 24, 2026.
Transparency logRelease files / continuo_validation_trino-0.1.1-py3-none-any.whl
| Download URL | continuo_validation_trino-0.1.1-py3-none-any.whl |
|---|---|
| Size | 4.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
27dce11e39288902b34987c81d085021a6d60258ba1832d782ae0a0261cfba85
|
|
BLAKE2b-256 checksum How to use checksums |
1b21ea4042eed993501c1f14360c4bcb3193e4bf283a4b5601917b503dd66c5e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.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 Jul 24, 2026.
Transparency log
