This release is a pre-release and may not be stable for production use.
DataHub Great Expectations (GX) Plugin
Send Great Expectations data quality results into DataHub — surface assertion outcomes alongside your dataset metadata so teams can see data health at a glance.
What you can do
- Emit assertion results from GX Checkpoints directly into DataHub as data quality assertions
- Link quality checks to datasets — results appear on the dataset's profile in DataHub
- Track pass/fail history over time for every expectation suite
- Works with any DataHub deployment — self-hosted or DataHub Cloud
Compatibility
| GX version | Module |
|---|---|
| 0.17.x / 0.18.x | datahub_gx_plugin.action.DataHubValidationAction |
| 1.x | datahub_gx_plugin.action_v1.DataHubValidationAction |
Both APIs are supported additively in the same package. Use the module that matches your installed GX major version.
Installation
pip install acryl-datahub-gx-plugin
Quickstart (GX 0.17 / 0.18)
Add the DataHub action to your GX Checkpoint:
from datahub_gx_plugin.action import DataHubValidationAction
from great_expectations.checkpoint import Checkpoint
checkpoint = Checkpoint(
name="my_checkpoint",
data_context=context,
action_list=[
{
"name": "datahub",
"action": {
"class_name": "DataHubValidationAction",
"module_name": "datahub_gx_plugin.action",
"server_url": "http://localhost:8080",
},
}
],
)
Quickstart (GX Core 1.x)
import great_expectations as gx
from datahub_gx_plugin.action_v1 import DataHubValidationAction
context = gx.get_context()
# ... create validation_definitions ...
checkpoint = context.checkpoints.add(
gx.Checkpoint(
name="my_checkpoint",
validation_definitions=validation_definitions,
actions=[
DataHubValidationAction(
name="datahub",
server_url="http://localhost:8080",
# Optional when batch_spec meta is incomplete:
# platform="postgres",
# dataset_name="public.my_table",
)
],
)
)
checkpoint.run()
Results from every Checkpoint run will appear in DataHub under the dataset's Validation tab.
Links
Metadata
Release files for acryl-datahub-gx-plugin 1.7.0.19rc1
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 |
|---|---|---|---|---|
| acryl_datahub_gx_plugin-1.7.0.19rc1.tar.gz | 19.8 kB | Without provenance | Details for acryl_datahub_gx_plugin-1.7.0.19rc1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| acryl_datahub_gx_plugin-1.7.0.19rc1-py3-none-any.whl | Python 3 | none | any | Details for acryl_datahub_gx_plugin-1.7.0.19rc1-py3-none-any.whl |
Total release size: 39.8 kB
Release files / acryl_datahub_gx_plugin-1.7.0.19rc1.tar.gz
| Download URL | acryl_datahub_gx_plugin-1.7.0.19rc1.tar.gz |
|---|---|
| Size | 19.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
94c9c82668b0bba5208a199087b86551b1f98a39f7b91a7a2ff3c0ee7e29c0a2
|
|
BLAKE2b-256 checksum How to use checksums |
02851f4b6c7a681aca8fddc7c3e8929f3e7b4b3479df6a264a448db19b6da0b0
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.10.22
|
Release files / acryl_datahub_gx_plugin-1.7.0.19rc1-py3-none-any.whl
| Download URL | acryl_datahub_gx_plugin-1.7.0.19rc1-py3-none-any.whl |
|---|---|
| Size | 20.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
41576f6d34061e88d9270323c0547d87574f6817e0a15396fb2ff5ef66db1c9b
|
|
BLAKE2b-256 checksum How to use checksums |
892e7aa10d98d2ccc698b8aad06bada0008d1d8d70f0b239e052afb305dadfa2
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.10.22
|
Security for acryl-datahub-gx-plugin 1.7.0.19rc1
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.