Fabio Picchi
06/05/2023, 12:54 PMFabio Picchi
06/05/2023, 12:55 PMVitaly Markov
06/05/2023, 2:56 PMFabio Picchi
06/06/2023, 10:51 AMFabio Picchi
06/06/2023, 10:51 AMFabio Picchi
06/06/2023, 11:29 AMdtm
asset is dtm_myproject
for the project "myproject" and we'll put them to separate asset groups so it is more convenient to trackFabio Picchi
06/06/2023, 11:31 AMVitaly Markov
06/06/2023, 4:05 PMFabio Picchi
06/07/2023, 6:28 AMFabio Picchi
06/07/2023, 10:30 AMsandy
06/07/2023, 3:10 PMI think this might work, but I haven't tested it yet. However, I am a bit worried whether asset keys are shared across code locations (I believe they are if they talk to the same dagster database). If that is the case, does that mean I would have to tag each asset, partition and job name with our project identifier?Asset keys need to be unique within a deployment, so you would need to tag the assets with the project identifier. The job name and partitions wouldn't need to be tagged with the project identifier. I think this is a reasonable approach, if the tagging them with the project identifier works for you.
Fabio Picchi
06/07/2023, 3:11 PMFabio Picchi
06/07/2023, 3:11 PMFabio Picchi
06/07/2023, 3:12 PMFabio Picchi
06/07/2023, 3:12 PM