You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Each pipeline run processes a single partition of data. A user defines an AssetStore that needs to know the partition of the data it’s storing. The body of compute_fns also need to know the partition of the data they’re processing.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
This is surely not the first time this has been proposed, but the new AssetStore APIs make it a little more important.
Motivation
Example: Two AssetStores on same underlying storage system
A user has both of these in the same pipeline:
They’d like to be able to configure the S3 region in only one place. They’d also like to be able to mock S3 in one place.
Example: AssetStore + shared pipeline-level config
Each pipeline run processes a single partition of data. A user defines an AssetStore that needs to know the partition of the data it’s storing. The body of compute_fns also need to know the partition of the data they’re processing.
Proposal
Circular dependencies would result in an error at definition time.
Remapping
Not part of MVP, but want to make sure it’s possible in the future.
Beta Was this translation helpful? Give feedback.
All reactions