Combining podcast provider API data into a single table

Summary

The user is trying to combine data from a podcast provider API into a single table but is facing issues with the number of rows being generated.


Question

Hell all! I’m fairly new to this, but I have a project for a client that I am hoping to scope.

I am pulling from their podcast provider API and I’m able to get the following with a call:
• list of all podcasts
• List of episodes per podcast
• List of downloads per episode
My hope is to create one combined table that gives me a running list of downloads for each episode of their podcasts over time.

However, in my setup I was producing WAY too many rows for my database… in theory it should only be something like 90K, but I had a sync producer over 3 million.



This topic has been created from a Slack thread to give it more visibility.
It will be on Read-Only mode here. Click here if you want to access the original thread.

Join the conversation on Slack

["podcast-provider-api", "combined-table", "data-sync", "database-rows"]