Skip to main content

convalesce-emit-gx

Forward Great Expectations validation results to Convalesce. Counts and statistics cross; row values never do.

Install

pip install convalesce-emit-gx

Wire it up

One class path serves both majors. convalesce_emit_gx.action picks the implementation for the installed Great Expectations.

On 1.x, list the action on the checkpoint:

from great_expectations import Checkpoint
from convalesce_emit_gx.action import ConvalesceValidationAction

checkpoint = Checkpoint(
    name="orders",
    validation_definitions=[...],
    actions=[ConvalesceValidationAction()],
)

On 0.x, list it in the checkpoint's action list:

action_list=[
    {
        "name": "convalesce",
        "action": {
            "module_name": "convalesce_emit_gx.action",
            "class_name": "ConvalesceValidationAction",
        },
    }
]

Set CONVALESCE_INGEST_KEY where the checkpoint runs.

Validating outside a checkpoint

Great Expectations runs actions only from a checkpoint. ValidationDefinition.run(), Batch.validate() and a 0.x Validator.validate() fire nothing, so send their result yourself:

from convalesce_emit_gx import forward_validation_result

result = validation_definition.run()
forward_validation_result(result)

On 0.x, pass the validator too, forward_validation_result(result, validator=validator), so the platform is named from its engine.

What crosses

  • Every field of the checkpoint result, each validation result and each expectation result, under every result format.
  • Each datasource's platform, database and default schema. Never its connection string; a password inside a batch spec is masked.
  • The query a query asset's batch is read with, up to 20,000 characters, so the tables and columns behind the batch can be read from it. Set CONVALESCE_SEND_SOURCE=false to keep it where it is.
  • Each result's GX Cloud page, when GX Cloud stored it.
  • Not the rows: sampled failing values, and the values a distinct-values or most-common-value expectation observed, cross as counts. Set CONVALESCE_GX_SEND_SAMPLES=true to send them.

Supported

Great Expectations 0.17 through 1.x, on Python 3.9 and later. Verified on real installs: see version-support.md.

Configure

Read from the environment: see convalesce-emit.

Metadata

Release files for convalesce-emit-gx 0.2.0

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for convalesce-emit-gx 0.2.0
File Size Uploaded
convalesce_emit_gx-0.2.0.tar.gz 38.5 kB Details

Built distribution (wheel)

Table of built distributions (wheels) for convalesce-emit-gx 0.2.0
File Interpreter ABI Platform
convalesce_emit_gx-0.2.0-py3-none-any.whl Python 3 none any Details

Total release size: 62.7 kB

Release files / convalesce_emit_gx-0.2.0.tar.gz

Download URL convalesce_emit_gx-0.2.0.tar.gz
Size 38.5 kB
Tags Source
SHA-256 checksum
How to use checksums
7cd81b7c41228f0bc60dd8f186ad87eaee5010c76649045b64e4e2650d322c7a
BLAKE2b-256 checksum
How to use checksums
220d49034e6a4d21de6814383be4c4480678ced9fb33e61e1fd4ac9c12f567d7
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 Oct 7, 2026.

Transparency log

Release files / convalesce_emit_gx-0.2.0-py3-none-any.whl

Download URL convalesce_emit_gx-0.2.0-py3-none-any.whl
Size 24.2 kB
Tags Python 3
SHA-256 checksum
How to use checksums
dc292e0a9b8da1e37f676c57767e5a9c9699e0c144a88164b36f1fbdf07ef9af
BLAKE2b-256 checksum
How to use checksums
e05bf0740411b7baf71a8c93bcf8bc189f8020aa5d9f60c4dff1484a5b3ea0b5
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 Oct 7, 2026.

Transparency log

Release history Release notifications | RSS feed

1.0.0

2 release files

0.3.0

2 release files

0.2.1

2 release files

This release

0.2.0 This release

2 release files

0.1.7

2 release files

0.1.6

2 release files

0.1.5

2 release files

0.1.4

2 release files

0.1.3

2 release files

0.1.1

2 release files

0.1.0

2 release files

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page