Magic ETL - filter with not in
Please forgive me if this is a stupid question but until this point all of my dataflows have been in mySQL or Redshift and I am trying to utilize the Magic ETL where possible looking for performance gains. Common scenario is to get a list of accounts and use that in a where clause to exclude those records from a result.
Example - select * from data where account not in(select account from exclusion_accounts)
This needs to be a dynamic list because the values are always changing so I cannot create a filter by with each value.
Can this be accomplished in Magic ETL?
Thank you.
-----------------
Chris
Best Answer
-
I would suggest creating a webform called "exclusion_accounts"
You could then bring that into your ETL as another input data set. Then join it to your table with an outer join so that you end up with only the accounts not in the exclusion data set.
Let me know if you need more details
“There is a superhero in all of us, we just need the courage to put on the cape.” -Superman2
Answers
-
I would suggest creating a webform called "exclusion_accounts"
You could then bring that into your ETL as another input data set. Then join it to your table with an outer join so that you end up with only the accounts not in the exclusion data set.
Let me know if you need more details
“There is a superhero in all of us, we just need the courage to put on the cape.” -Superman2 -
Thank you. Thinking about the magic etl flow differently than typical sql had me turned around a bit. My list of exclusion account numbers are available from another dataset but I was stuck on the not in syntax and did not think about outer joining and filtering the nulls.
Thanks again.
-----------------
Chris1 -
There is definitely a bit of a learning curve when trying to switch from MySQL to ETL data flows. I find myself using a lot of both. Somethings make more sense to me in ETL (particularly collapsing or uncollapsing data sets and windowed functions) while other things seem easier to do in MySQL.
The biggest pointer that I can offer to the ETL dataflows is to always name your tiles with something that will tell you exactly what the step is doing
“There is a superhero in all of us, we just need the courage to put on the cape.” -Superman1
Categories
- All Categories
- 1.8K Product Ideas
- 1.8K Ideas Exchange
- 1.5K Connect
- 1.2K Connectors
- 300 Workbench
- 6 Cloud Amplifier
- 8 Federated
- 2.9K Transform
- 100 SQL DataFlows
- 616 Datasets
- 2.2K Magic ETL
- 3.8K Visualize
- 2.5K Charting
- 738 Beast Mode
- 56 App Studio
- 40 Variables
- 684 Automate
- 176 Apps
- 452 APIs & Domo Developer
- 46 Workflows
- 10 DomoAI
- 35 Predict
- 14 Jupyter Workspaces
- 21 R & Python Tiles
- 394 Distribute
- 113 Domo Everywhere
- 275 Scheduled Reports
- 6 Software Integrations
- 123 Manage
- 120 Governance & Security
- 8 Domo Community Gallery
- 38 Product Releases
- 10 Domo University
- 5.4K Community Forums
- 40 Getting Started
- 30 Community Member Introductions
- 108 Community Announcements
- 4.8K Archive