Eliza DQ validates any data source with a single API. Point it at a warehouse table, a parquet file, a pandas DataFrame, or a database URI and get results in milliseconds.

pip install eliza-dq

On a warehouse (BigQuery, Athena, Snowflake, ...)

# eliza_checks/orders.yaml
connection:
  type: bigquery
  project: my-project-123

table: my-project-123.analytics.orders
sample_id: order_id    # optional: cheaper sample queries on wide tables

checks:
  - column: order_id
    check: not_null
  - column: amount
    check: not_negative
  - column: updated_at
    check: freshness
    max_age: 24h

pip install eliza-dq[bigquery]
eliza check --config orders

On a DataFrame or file

from eliza import check

# Polars DataFrame, pandas DataFrame, parquet, CSV, ndjson - all work
result = check("data.parquet", checks={
    "order_id": ["not_null", "unique"],
    "amount":   ["not_null", "not_negative"],
    "email":    ["is_email"],
})
result.raise_on_fail()

On a production database (without running heavy queries on prod)

connection:
  type: postgres
  host: prod-db.internal
  user: readonly
  password: ${DB_PASSWORD}
  database: production

engine: local    # pulls data, checks locally with Polars
table: orders
filter: "created_at >= '2024-01-01'"

checks:
  - column: order_id
    check: not_null

Why Eliza

• You control what gets scanned - sample_id and sample_columns let you choose exactly which columns appear in sample queries. On per-byte warehouses (BQ, Athena) this cuts sample costs by up to 92% on wide tables. Soda always runs SELECT *
• Optimized SQL - parallel sample collection, COUNT(CASE...THEN 1 END) aggregation, HAVING COUNT(*) for cross-dialect compatibility. 1.1-2.2x faster than Soda across 10 tested tables without any caching
• Handles datasets that crash other tools - Polars LazyFrame streaming validates 259M rows from disk in 1.9s with constant memory. Pandera and GX OOM
• 2-3x faster on DataFrames than Pandera at constant memory
• Lightweight - 2 dependencies (polars + pyyaml) vs 30+ for Soda/GX
• Works with any source - same API for 8 warehouse connectors, parquet/CSV files, Polars/pandas DataFrames, and production databases
• PDF reports and Slack alerts built-in

Benchmarks

SQL Pushdown (Eliza vs Soda Core)

8 identical not_null checks + failed row samples. Both tools batch checks into a single SELECT. Both use LIMIT on sample queries. All measurements with use_query_cache=False. 3 interleaved runs, median time.

AWS Athena (Iceberg):

Eliza is 1.6-1.8x faster on Athena. Advantage comes from parallel sample collection and lighter client (~176ms init vs ~350ms). On Athena, each query has fixed overhead (Glue metadata, S3 listing, queue), and parallel execution avoids paying it sequentially.

BigQuery on-demand (fresh tables, use_query_cache=False):

DWH cost with sample_id (BQ on-demand $6.25/TB, Athena $5/TB):

_{Eliza gives you control over what gets scanned in sample queries. With sample_id, samples scan only 2 columns (ID + failing column) instead of SELECT * over all columns. BQ/Athena charge per byte scanned, so fewer columns = proportionally cheaper. On a 56-column table with 6 failing checks: 6 queries x 56 cols vs 6 queries x 2 cols = 28x less data scanned. You can also use sample_columns to pick exactly which columns to include. Aggregation cost is always the same -- both tools scan only the checked columns. Without sample_id, Eliza and Soda cost the same.}

DataFrame Engine

NYC Yellow Taxi (Parquet). 5 checks, warmup + 3 runs, min time.

When the DataFrame is already in memory (notebook, mid-pipeline step):

All tools check everything (Pandera with lazy=True). Eliza returns fail counts, fail rates, and sample rows. Others raise an exception or return less detail.

_{Eliza is 24x faster than Pandera and 41x faster than Dataframely on 126M rows. GX includes pandas conversion (real-world usage). 126M tested with 4 columns to fit in RAM.}

What you get back when checks fail:

When reading from files (S3, CI runner, Lambda, cron job):

Competitors need the entire dataset in memory as a DataFrame before running checks. Eliza streams via Polars LazyFrames and never loads the full dataset.

Eliza's peak RAM stays under 1 GB at all tested scales -- data streams through in chunks via Polars LazyFrames. Competitors must load all files into a single DataFrame first. At 259M rows with all columns that's 7.6+ GB, enough to OOM an 8 GB Lambda or CI runner. Streaming is a feature of Polars; Eliza's value is that 17 checks, fail counts, sample rows, and reports come on top of it. Reproducible: python benchmarks/dataframe.py --full

Eliza vs Soda Core

_{Soda runs SELECT * for samples and by default discards the rows (DefaultSampler). To see them, you need scan.sampler = LogSampler() in Python -- not available from CLI or YAML. Even with LogSampler, it's still SELECT * over all columns. The sample limit is configurable in both tools (Soda default 100, Eliza default 10), but on BigQuery and Athena LIMIT doesn't reduce cost -- price is determined by columns in SELECT, not rows returned. One SELECT * sample query on a 56-column table costs the same as a full scan. Eliza by default selects only the checked columns, and with sample_id narrows further to ID + failing column.}

Features

Checks

17 built-in checks, all work on both Polars and SQL:

Warehouse Connectors

Install only what you need:

pip install eliza-dq[bigquery]
pip install eliza-dq[athena]
pip install eliza-dq[snowflake]
pip install eliza-dq[postgres]
pip install eliza-dq[clickhouse]
pip install eliza-dq[mysql]
pip install eliza-dq[databricks]
pip install eliza-dq[redshift]

# BigQuery
connection:
  type: bigquery
  project: my-project
  location: US

# Athena
connection:
  type: athena
  region: us-east-1
  schema: my_database
  s3_staging_dir: s3://bucket/athena-results/

# Snowflake
connection:
  type: snowflake
  account: xy12345.us-east-1
  user: eliza_user
  password: ${SF_PASSWORD}
  warehouse: COMPUTE_WH
  database: ANALYTICS
  schema: PUBLIC

# PostgreSQL
connection:
  type: postgres
  host: localhost
  port: 5432
  user: postgres
  password: ${PG_PASSWORD}
  database: mydb

# MySQL
connection:
  type: mysql
  host: localhost
  user: root
  password: ${MYSQL_PASSWORD}
  database: mydb

# ClickHouse
connection:
  type: clickhouse
  host: localhost
  port: 8123
  user: default
  database: mydb

# Databricks
connection:
  type: databricks
  host: adb-123.azuredatabricks.net
  http_path: /sql/1.0/warehouses/abc
  token: ${DBX_TOKEN}

# Redshift
connection:
  type: redshift
  host: cluster.region.redshift.amazonaws.com
  database: analytics
  user: eliza_user
  password: ${RS_PASSWORD}

Alerting & Reporting

from eliza import check
from eliza.alert import send_slack, send_webhook
from eliza.report import generate_pdf

result = check(config="orders")

# Slack - choose any channel, attach PDF
send_slack(
    result,
    token="xoxb-...",
    channel="C0ALERTS",
    pdf=True,
    name="orders",
)

# PDF report
generate_pdf(result, name="orders")

# Generic webhook (Discord, Teams, PagerDuty)
send_webhook(result, url="https://your-webhook-url/...")

pip install eliza-dq[report]  # for PDF reports

Slack Alert

PDF Report

Orchestrator Integration

Airflow

@task
def dq_check():
    from eliza import check
    from eliza.alert import send_slack

    result = check(config="orders")

    if not result.passed():
        send_slack(result, token="xoxb-...", channel="C...", pdf=True, name="orders")

    result.raise_on_fail()
    return result.to_dict()

Dagster

@asset_check(asset=orders)
def orders_quality():
    from eliza import check
    result = check(config="orders")
    return AssetCheckResult(
        passed=result.passed(),
        metadata={"summary": result.summary()},
    )

GitHub Actions

steps:
  - run: pip install eliza-dq
  - run: eliza check --config orders --source data/orders.parquet

Any orchestrator

result = check(config="orders")

result.raise_on_fail()   # RuntimeError (Airflow, Dagster, Prefect)
result.exit_code         # 0/1/2 (bash, CLI, GitHub Actions)
result.to_dict()         # dict (XCom, metadata)
result.to_json()         # JSON string (APIs)
result.summary()         # "3 passed, 1 failed (1M rows, 42ms)"

Architecture

SQL pushdown: All inline checks batched into one SELECT (single table scan). Separate checks (unique, freshness) and sample queries run in parallel via ThreadPoolExecutor with thread-local connections. Samples use SELECT column_list with LIMIT N instead of SELECT *.

Polars engine: Streaming with per-column grouping. Files scanned as LazyFrames - data streams through without loading into RAM. Failed row samples via .filter().head(N).collect(engine="streaming").

OLTP mode: engine: local pulls data through the connector, checks locally with Polars. Safe for production databases.

License

MIT