Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Report ETL quality as Dagster asset checks with WARN and ERROR severity

Open
  • Is something wrong?
#345 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
34/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
python
Domain
data-engineering, observability

Research direction

Start by reading the roadmap references #183, #23, #22, and #209, then trace how Floe reports and dbt test results enter Dagster today. Define how Silver report outcomes and Gold dbt severities become asset checks, and verify the acceptance criteria for WARN continuation, ERROR blocking, log links, and alert delivery on the slim preset.

Written by the indexing model from the issue text.

Description

priority: P0 roadmap track: observability

Milestone: v0.7-alpha — Observability and Data Quality
Roadmap sequence: #183 (revised 2026-10-05)

Context

Floe already applies a per-entity policy (policy: { severity: "reject" }) and writes reports, and dbt projects can declare tests, but a run today only succeeds or fails: there is no warning level, no thresholds, and quality outcomes are not first-class in the orchestrator. Operators need errors that stop bad data and warnings that do not.

Scope

  • Turn Floe report outcomes into Dagster asset checks per Silver table: rows read/accepted/rejected, rejection rate against a contract-declared threshold, schema or cast failures.
  • Turn dbt tests on Gold into asset checks, keeping dbt's warn/error severities.
  • Severity semantics: ERROR fails the asset and blocks downstream materialization; WARN records the result and lets the run continue. Thresholds live in user code (Floe contract, dbt YAML), not in shared platform code (rule 5).
  • Results feed the alert rules (#23), are correlated with logs (#22) by stage/product/run, and are the signal source #209 defines.
  • Works on the slim preset without OpenMetadata.

Acceptance criteria

  • A rejection rate above the warning threshold produces a WARN check and a completed run; above the error threshold the run fails and downstream assets do not run.
  • A failing dbt test with severity: warn warns; with error fails.
  • Every check names stage, product, table and run, and links to its logs.
  • A WARN and an ERROR each reach the test receiver through #23.
Dominant language
Python
Stars
26
Forks
6
Avg merge
12h 10m
Merged PRs (30d)
175

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from OpenLakeForge/openlakeforge

All issues in OpenLakeForge/openlakeforge

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.