Christopher DeCarolis
Christopher DeCarolis
In the days of FreshnessPolicys, users could use DagsterDbtTranslator to allow setting up per-model freshness expectations in their model config. With freshness checks, this is no longer straightforward to do....
Uses the newly added get_asset_check_summary_record to implement the freshness check sensor. Adds some more tests for previously under-handled cases; having an asset which is currently in planned state, and ensuring...
Relevant error message is [here](https://github.com/dagster-io/dagster/blob/9444b2fc8458131f2fdb95971bf6c8c6929915c2/python_modules/dagster/dagster/core/execution/memoization.py#L30). States that in-memory io managers cannot be used, but doesn't directly check whether in memory io managers are used. I _think_ that it should be...
There are cases where users can easily end up with the same assets definition object floating around in multiple places. Consider the following case: - asset my_asset is in module...
The `assets` property on definition did something very different from `get_assets_def` property, and I found that very confusing. The only reason we needed public properties for the "dagster defs" within...
Publicize AssetCheckSummaryRecord and kin. This API is quite useful for creating sensors that might make use of an asset check's result. See: https://github.com/dagster-io/dagster/discussions/22176
Currently, software-defined assets declare their dependencies via inputs to the underlying node. Sometimes, it's advantageous to declare dependencies without having the dependency correspond to an input. In cases such as...
Abandoned this PR in favor of https://github.com/dagster-io/dagster/pull/23956
Make the readme more new-user friendly. Walks through all the APIs more concretely.
Renames dbt-example to airlift-demo, to reflect the nature of its use