Run Preview in magic ETL seems not quite there
Comments
-
When you are testing the logic, I would add on a lot of filters to narrow down the data sets. Rather than sales accross the globe, focus on one country, or even one city. If you apply the same filters to each dataset as you are "previewing" the data; you should be able to see how the joins are performing. Once you are happy with it, remove those filters and let the data set run. Then validate the output dataset.
“There is a superhero in all of us, we just need the courage to put on the cape.” -Superman1 -
If I understand correctly, you advice me to create sampled versions of my input data sets for ETL debugging and avoid using the Run Preview feature altogether? Cause for that's what we've beeen doing here and are very pleased with how it works. We would, however, find it much smoother to use a run preivew button that uses some smart sampling mechanism (event random would be better than simply taking the first 100 or so rows)
1
Categories
- All Categories
- 1.1K Product Ideas
- 1.1K Ideas Exchange
- 1.2K Connect
- 969 Connectors
- 257 Workbench
- Cloud Amplifier
- 1 Federated
- 2.4K Transform
- 76 SQL DataFlows
- 501 Datasets
- 1.8K Magic ETL
- 2.7K Visualize
- 2.2K Charting
- 378 Beast Mode
- 20 Variables
- 486 Automate
- 104 Apps
- 378 APIs & Domo Developer
- 6 Workflows
- 22 Predict
- 6 Jupyter Workspaces
- 16 R & Python Tiles
- 317 Distribute
- 65 Domo Everywhere
- 252 Scheduled Reports
- 59 Manage
- 59 Governance & Security
- 1 Product Release Questions
- 5K Community Forums
- 37 Getting Started
- 23 Community Member Introductions
- 64 Community Announcements
- 4.8K Archive