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
how would an ETL like the following need to be broken down in dagster when using the (multi-) asset functionality and how many credits would it cost to materialize 7 partitions with it?
Extracting Data from an API (1 endpoint for aggregate, 2 endpoints for masterdata)
Transforming the data (standardising column names, etc) for each of these
Loading the data for each of these into separate staging tables
Merging the data in each of the staging tables into the main data table
My current idea is you need the following for each materialization:
Three ops for Extract
Three ops for Transform
Three ops for Load
Three ops for Merge
Three asset materialisations for the multi-asset
Which would be 15 credits x 7 materialisations, or 105 credits.
I'm assuming the same applies for single-run backfills.
Is this correct?
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
-
Hello,
how would an ETL like the following need to be broken down in dagster when using the (multi-) asset functionality and how many credits would it cost to materialize 7 partitions with it?
My current idea is you need the following for each materialization:
Which would be 15 credits x 7 materialisations, or 105 credits.
I'm assuming the same applies for single-run backfills.
Is this correct?
Beta Was this translation helpful? Give feedback.
All reactions