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.
1 -
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.9K Product Ideas
- 1.9K Ideas Exchange
- 1.6K Connect
- 1.3K Connectors
- 302 Workbench
- 6 Cloud Amplifier
- 9 Federated
- 2.9K Transform
- 104 SQL DataFlows
- 637 Datasets
- 2.2K Magic ETL
- 3.9K Visualize
- 2.5K Charting
- 761 Beast Mode
- 65 App Studio
- 42 Variables
- 703 Automate
- 182 Apps
- 458 APIs & Domo Developer
- 53 Workflows
- 10 DomoAI
- 39 Predict
- 16 Jupyter Workspaces
- 23 R & Python Tiles
- 401 Distribute
- 116 Domo Everywhere
- 277 Scheduled Reports
- 8 Software Integrations
- 132 Manage
- 129 Governance & Security
- 8 Domo Community Gallery
- 38 Product Releases
- 12 Domo University
- 5.4K Community Forums
- 40 Getting Started
- 30 Community Member Introductions
- 111 Community Announcements
- 4.8K Archive