Auto materialize triggers different assets groups in the same run about dagster HOT 5 CLOSED

Hey @chrishiste - you can use AutoMaterializeSensorDefinitions to execute them independently:

from dagster import AutoMaterializeSensorDefinition

group1_auto_materialize_sensor = AutoMaterializeSensorDefinition(
    "group1_sensor", asset_selection=AssetSelection.groups("group1")
)

group2_auto_materialize_sensor = AutoMaterializeSensorDefinition(
    "group2_sensor", asset_selection=AssetSelection.groups("group2")
)

defs = Definitions(sensors=[group1_auto_materialize_sensor, group2_auto_materialize_sensor])

cc @gibsondan to correct me if I got any of this wrong

from dagster.

That is correct, but I would recommend upgrading to 1.6.9 or later before using AutoMaterializeSensorDefinition as there were some fixes related to them in that release.

from dagster.

@sryza awesome :)

Currently I don't have anything setup for auto materialization, I just turned it on globally. How will a dedicated sensor cohabit with the global auto materialization? Do I need to turn that off and create specific sensors for all my groups?

from dagster.

@chrishiste We should have mentioned that you enable this feature via your dagster.yaml as well:

auto_materialize:
  use_sensors: true

or if you're using the Dagster helm chart:

additionalInstanceConfig:
  auto_materialize:
    use_sensors: true

Docs for all of this coming soon!

from dagster.

@gibsondan that makes sense. I will wait for the docs to implement thanks.

from dagster.