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

Publish data-quality results to OpenMetadata

Open
  • Is something wrong?
#346 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
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
python
Domain
data-engineering, databases

Research direction

Start by reading ADR 0007 and the implementation of governance capability and artifact processing; the issue gives no file paths, so locate these entry points in the repository. Verify whether the pinned OpenMetadata version ingests OpenLineage data-quality facets, then record the Silver integration decision in ADR 0007. Done means Gold dbt and Silver Floe results have per-table history, WARN and ERROR are distinguishable, and disabled governance publishes nothing.

Written by the indexing model from the issue text.

Description

priority: P1 roadmap track: governance

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

Context

Analysts discover tables in OpenMetadata, but they cannot see whether a table passed its quality checks. ADR 0007 keeps lineage engine-emitted (OpenLineage) and rejects a custom REST push for lineage; quality results from Floe have no native path into OpenMetadata, so this needs a decision first.

Scope

  • Gold: ingest dbt test results through OpenMetadata's native dbt ingestion (run_results.json) during the artifacts phase.
  • Silver: publish Floe-derived check results from #345 as OpenMetadata test cases and results. Decide and record in ADR 0007 between (a) an explicit, contained exception where olf writes quality results, recommended, or (b) Floe emitting OpenLineage data-quality facets, if OpenMetadata ingests them (verify against the pinned version).
  • Pass/warn/fail history per table visible in the catalog; credentials through the existing OpenMetadata Secret reference.
  • Only when the governance capability is enabled; a disabled capability publishes nothing and fails nothing.

Out of scope

  • Ownership, classification and SLA semantics (#54, v1.0), which will generate expectations onto this mechanism.
  • Profiling and sample data (#56).

Acceptance criteria

  • Gold dbt test results and Silver Floe check results appear on their OpenMetadata tables with history.
  • A WARN and an ERROR from #345 are distinguishable in OpenMetadata.
  • ADR 0007 records the quality-results decision.
  • Without the governance capability the pipeline behaves identically and publishes nothing.
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.