ClickHouse dialect for SQLAlchemy for Superset.
Installation
The package is installable through PIP:
pip install superset-clickhouse
Usage
The DSN format is similar to that of regular Postgres:
>>> import sqlalchemy as sa
>>> sa.create_engine('clickhouse://username:password@hostname:port/database')
Engine('clickhouse://username:password@hostname:port/database')
For SSL add ssl parameter to URL:
>>> import sqlalchemy as sa
>>> sa.create_engine('clickhouse://username:password@hostname:port/database?ssl=True')
Engine('clickhouse://username:password@hostname:port/database')
It implements a dialect, so there’s no user-facing API.
1 maintainer
Metadata
1 maintainer
Release files for superset-clickhouse 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 | Provenance | Actions |
|---|---|---|---|---|
| superset-clickhouse-0.1.1.tar.gz | 13.9 kB | Without provenance | Details for superset-clickhouse-0.1.1.tar.gz |
Release files / superset-clickhouse-0.1.1.tar.gz
| Download URL | superset-clickhouse-0.1.1.tar.gz |
|---|---|
| Size | 13.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
61bc9c1e6296f799dedfaeb93bd138ecab675608304a558290442a4c177e9ea7
|
|
BLAKE2b-256 checksum How to use checksums |
6120c874c6346202f002bb59277aac726ce7d5fe5c5cdacc83ae29f2537abcd7
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.4.1 importlib_metadata/4.3.0 pkginfo/1.7.0 requests/2.25.1 requests-toolbelt/0.9.1 tqdm/4.61.0 CPython/3.8.5
|
Security for superset-clickhouse 0.1.1
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.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A 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.
