PUDL has a few pre-configured jobs and about a dozen asset groups. For example, we have a job that runs the ETL for all available years called etl_full and another job that runs the ETL for the most recent year of data called etl_fast:
When I click on an asset group and select "Materialize All", dagster uses the default configuration. It would be nice to be able to execute one asset group like clean_eia860 using the configuration of the etl_fast job.
Ideas of implementation
I think this could be achieved by being able to filter assets in Dagit using asset group name. Something like this:
Additional information
Originated from this discussion question #13792
Message from the maintainers
Impacted by this issue? Give it a 👍! We factor engagement into prioritization.
What's the use case?
PUDL has a few pre-configured jobs and about a dozen asset groups. For example, we have a job that runs the ETL for all available years called
etl_full
and another job that runs the ETL for the most recent year of data calledetl_fast
:When I click on an asset group and select "Materialize All", dagster uses the default configuration. It would be nice to be able to execute one asset group like
clean_eia860
using the configuration of theetl_fast
job.Ideas of implementation
I think this could be achieved by being able to filter assets in Dagit using asset group name. Something like this:
Additional information
Originated from this discussion question #13792
Message from the maintainers
Impacted by this issue? Give it a 👍! We factor engagement into prioritization.