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

dagster

Question... If I'm loading a set of Airbyte assets via `load_assets_from_airbyte_instance`, and the connections are scheduled on the Airbyte side, and I'm using `build_asset_reconciliation_sensor`, will Dagster automatically detect when a connection sync has updated a set of tables by querying the state of the Airbyte instance, so that downstream assets will be materialized?

<@U011CET83FG> do you happen to know the answer, or can you point me at someone who does? Ideally I'd like to have Airbyte run on its schedule, and then have Dagster detect those updates and materialize downstream assets.

(Responded in the Airbyte Slack, but leaving here for posterity): right now Dagster only creates asset materializations when it triggers an Airbyte sync. This is potentially something we could support down the line using source asset observations (<https://docs.dagster.io/concepts/assets/asset-observations#observable-source-assets>)