Asset Materialization

An asset materialization records or represents production of a named data asset, such as a table or file. Its meaning depends on the orchestrator and integration: identify which physical output, partition, and version the event describes.

An asset key names a logical result; it is not necessarily a unique immutable object version. Record input and code versions when reproducibility matters, and distinguish a successful production attempt from a verified consumer-visible commit.

A materialization event alone does not prove source completeness, business correctness, freshness, or durable storage. An in-memory demonstration can produce materialization events without creating a lasting table. Use destination and quality evidence for those separate claims.

For daily_sales on October 2, retain the partition key, output table or object reference, input revision, code version, and validation result with the production record. If that date is rebuilt, the logical asset name stays the same while its physical version can change. Consumers that need reproducibility must be able to resolve the intended version rather than simply reading the latest object bearing that name.

See Asset-Oriented Orchestration: Dagster and Prefect for worked examples.

Further reading

• Dagster: Assets