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.7K Product Ideas
- 1.7K Ideas Exchange
- 1.5K Connect
- 1.2K Connectors
- 292 Workbench
- 4 Cloud Amplifier
- 8 Federated
- 2.8K Transform
- 95 SQL DataFlows
- 603 Datasets
- 2.1K Magic ETL
- 3.7K Visualize
- 2.4K Charting
- 697 Beast Mode
- 43 App Studio
- 39 Variables
- 658 Automate
- 170 Apps
- 441 APIs & Domo Developer
- 42 Workflows
- 5 DomoAI
- 32 Predict
- 12 Jupyter Workspaces
- 20 R & Python Tiles
- 386 Distribute
- 111 Domo Everywhere
- 269 Scheduled Reports
- 6 Software Integrations
- 113 Manage
- 110 Governance & Security
- 8 Domo University
- 30 Product Releases
- Community Forums
- 40 Getting Started
- 30 Community Member Introductions
- 98 Community Announcements
- Domo Community Gallery
- 4.8K Archive