Repository navigation
fix(dagster-openlineage): emit asset run-start without a placeholder output - #345
Open
dan-newton-sparta wants to merge 1 commit into
Open
dan-newton-sparta wants to merge 1 commit into
dan-newton-sparta wants to merge 1 commit into
Conversation
…output A planned/START event has no materialization metadata yet — no inputs, no schema or column facets. It previously emitted a bare output dataset anyway, which makes backends that build lineage edges from every event create a spurious output-only edge with no input side. Emit START as a pure run-start signal; the COMPLETE event still carries the inputs, outputs, and facets.
dan-newton-sparta
force-pushed
the
feat/openlineage-run-start-no-output
branch
from
September 9, 2026 18:34
52ad736 to
7bfae2e
Compare
dan-newton-sparta
marked this pull request as ready for review
September 9, 2026 18:44
This was referenced Sep 11, 2026
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
ASSET_MATERIALIZATION_PLANNEDemitted a placeholder output dataset with no inputs and no facets. This change emits it as a pure run-start; theCOMPLETEevent still carries the full inputs, outputs, and facets.Summary & Motivation
A planned/START event has no materialization metadata yet — no inputs, no schema, no column lineage. For lineage backends that build edges from every event this can produce an output-only edge with no input side. Emitting START as a pure run-start signal keeps the run-start semantics while deferring all dataset/facet information to
COMPLETE, where it is actually known.How I Tested These Changes
COMPLETEstill carries the output.uv run pytestgreen;ruff check,ruff format --check, andty check .clean.Changelog
Added a
### Changedentry under## [Unreleased]inCHANGELOG.md.Related changes
Part of a set of small improvements to Dagster → OpenLineage. The lineage-fidelity changes are each independent and mergeable on their own; the ownership pair is stacked (#354 builds on #353).
Lineage fidelity:
exclude_asset_keysto the storage wrapperOwnership: