Jamie Lee
02/01/2023, 11:29 AMasset_selection
and asset_keys
? Example in 🧵prod_data
is a just an asset materialisation. This currently does not pull through the prod_data asset key into the asset sensor cursor. Is it possible to use both?
@multi_asset_sensor(
asset_selection=AssetSelection.assets(
*fivetran_csv_seed_assets,
*fivetran_braintree_assets,
*fivetran_salesforce_assets,
*fivetran_intercom_assets,
),
asset_keys=[AssetKey("prod_data")],
job=main_pipeline,
name="trigger_main_pipeline",
)
def trigger_main_pipeline(context):
...
jamie
02/01/2023, 5:00 PMprod_data
to your AssetSelection like this
asset_selection=AssetSelection.assets(
*fivetran_csv_seed_assets,
*fivetran_braintree_assets,
*fivetran_salesforce_assets,
*fivetran_intercom_assets,
) | AssetSelection.keys("prod_data"),
and then remove the asset_keys
parameterJamie Lee
02/02/2023, 10:01 AMAssetKey(s) {AssetKey(['prod_data'])} were selected, but no AssetsDefinition objects supply these keys. Make sure all keys are spelled correctly, and all AssetsDefinitions are correctly added to the repository.
As mentioned the AssetKey(['prod_data'])
is just an AssetMaterialisation. Should this still work?jamie
02/02/2023, 2:28 PMprod_data
is just an asset materialization. in that case, I don’t believe this will work