Skip to content

crash242/S3-Data-Lake

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

12 Commits
 
 
 
 
 
 
 
 
 
 

Repository files navigation

A music streaming startup, Sparkify, has grown their user base and song database even more and want to move their data warehouse to a data lake. Their data resides in S3, in a directory of JSON logs on user activity on the app, as well as a directory with JSON metadata on the songs in their app

The purpose of this project is to build an ETL pipeline that extracts their data from S3, processes them using Spark, and loads the data back into S3 as a set of dimensional tables. This will allow their analytics team to continue finding insights in what songs their users are listening to.

Project Datasets You'll be working with two datasets that reside in S3. Here are the S3 links for each: Song data: s3://udacity-dend/song_data Log data: s3://udacity-dend/log_data

Schema for Song Play Analysis

Using the song and log datasets, you'll need to create a star schema optimized for queries on song play analysis. This includes the following tables.

Fact Table

  • songplays (records in log data associated with song plays i.e. records with page NextSong) - songplay_id, start_time, user_id, level, song_id, artist_id, session_id, location, user_agent

Dimension Tables

  • users (users in the app) - user_id, first_name, last_name, gender, level
  • songs (songs in music database) - song_id, title, artist_id, year, duration
  • artists (artists in music database) - artist_id, name, location, lattitude, longitude
  • time (timestamps of records in songplays broken down into specific units) - start_time, hour, day, week, month, year, weekdays

Schema for Song Play Analysis

Using the song and log datasets, you'll need to create a star schema optimized for queries on song play analysis. This includes the following tables.

Fact Table

  • songplays (records in log data associated with song plays i.e. records with page NextSong) - songplay_id, start_time, user_id, level, song_id, artist_id, session_id, location, user_agent

Dimension Tables

  • users (users in the app) - user_id, first_name, last_name, gender, level
  • songs (songs in music database) - song_id, title, artist_id, year, duration
  • artists (artists in music database) - artist_id, name, location, lattitude, longitude
  • time (timestamps of records in songplays broken down into specific units) - start_time, hour, day, week, month, year, weekdays

About

No description, website, or topics provided.

Resources

Stars

Watchers

Forks

Releases

No releases published

Packages