Hi team I am currently working on migrating our extract amp

Question

Hi team I am currently working on migrating our extract amp load jobs to adopt the concept of software defined assets first step towards adopting declarative scheduling with dbt down the road Our E amp L jobs heavily relied on a common set of graphs We create different jobs using `<http dagster graph to|dagster graph to> job` with different config and resource defs etc If I understand the concept correct each asset graph backed asset is supposed to be unique and has a unique identifier key Do I have to convert the following graph ``` graph def batch mongo graph data = extract mongo op validated = deserialise json data df = validated to dataframe validated load redshift batch df another graph executing commands to load data from s3 to redshift``` to something like ``` graph asset def mongo extract load asset one data = extract mongo op start=job is defined validated = deserialise json data df = validated to dataframe validated load redshift batch df graph asset def mongo extract load asset two data = extract mongo op start=job is defined validated = deserialise json data df = validated to dataframe validated load redshift batch df ``` How do I specify run time configurations of the graph assets and also how do I turn them into jobs

Bolin Zhu · Answer

One more follow up question can we turn graphs that do not return anything into graph backed asset I tried ```asset one = AssetsDefinition from graph asset one job = define asset job name= asset one defs = Definitions assets= asset one jobs= asset one job ``` I am getting this error ```dagster check CheckError Invariant failed Description All leaf nodes within graph batch mongo graph must generate outputs which are mapped to outputs of the graph and produce assets The following leaf node s are non asset producing ops load redshift batch This behavior is not currently supported because these ops are not required for the creation of the associated asset s ```