The cloud-native orchestrator for the whole development lifecycle, with integrated lineage and observability.

dagster

Asset scheduling question: is there a way to create a `@sensor` that runs only when an asset is materialized _and_ the materialized contents are different from the last time it was materialized?

Actually even better is it possible to write the `@asset` operation so that it only emits new asset data if it has changed?

I figured out a method to do this using the technique described here: <https://stackoverflow.com/questions/73983827/how-can-i-do-an-incremental-load-based-on-record-id-in-dagster>