|
| 1 | +# Redshift Data Warehouse |
| 2 | + |
| 3 | +### Introducion |
| 4 | +A music streaming startup, Sparkify, has grown their user base and song database and want to move their processes and data onto the cloud. 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. |
| 5 | +We will build an ETL pipeline that extracts their data from S3, stages them in Redshift, and transforms data into a set of dimensional tables for their analytics team to continue finding insights in what songs their users are listening to. |
| 6 | + |
| 7 | +#### Project Datasets |
| 8 | +You'll be working with two datasets that reside in S3. Here are the S3 links for each: |
| 9 | +> Song data: s3://udacity-dend/song_data |
| 10 | +> Log data: s3://udacity-dend/log_data |
| 11 | +
|
| 12 | +Log data json path: s3://udacity-dend/log_json_path.json |
| 13 | + |
| 14 | +#### Song Dataset |
| 15 | +The first dataset is a subset of real data from the [Million Song Dataset](https://labrosa.ee.columbia.edu/millionsong/). Each file is in JSON format and contains metadata about a song and the artist of that song. The files are partitioned by the first three letters of each song's track ID. For example, here are filepaths to two files in this dataset. |
| 16 | +> song_data/A/B/C/TRABCEI128F424C983.json |
| 17 | +> song_data/A/A/B/TRAABJL12903CDCF1A.json |
| 18 | +
|
| 19 | +And below is an example of what a single song file, TRAABJL12903CDCF1A.json, looks like. |
| 20 | + {"num_songs": 1, "artist_id": "ARJIE2Y1187B994AB7", "artist_latitude": null, "artist_longitude": null, "artist_location": "", "artist_name": "Line Renaud", "song_id": "SOUPIRU12A6D4FA1E1", "title": "Der Kleine Dompfaff", "duration": 152.92036, "year": 0} |
| 21 | + |
| 22 | +#### Log Dataset |
| 23 | +The second dataset consists of log files in JSON format generated by this [event simulator](https://github.com/Interana/eventsim) based on the songs in the dataset above. These simulate activity logs from a music streaming app based on specified configurations. |
| 24 | +The log files in the dataset you'll be working with are partitioned by year and month. For example, here are filepaths to two files in this dataset. |
| 25 | +> log_data/2018/11/2018-11-12-events.json |
| 26 | +> log_data/2018/11/2018-11-13-events.json |
| 27 | +
|
| 28 | +And below is an example of what the data in a log file, 2018-11-12-events.json, looks like. |
| 29 | + |
| 30 | + |
| 31 | + |
| 32 | +#### Schema for Song Play Analysis |
| 33 | +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. |
| 34 | +##### Fact Table |
| 35 | +1.**songplays** - records in log data associated with song plays i.e. records with page ***NextSong*** |
| 36 | +- start_time, user_id, level, song_id, artist_id, session_id, location, user_agent |
| 37 | + |
| 38 | +##### Dimension Tables |
| 39 | +2.**users** - users in the app |
| 40 | +- user_id, first_name, last_name, gender, level |
| 41 | + |
| 42 | +3.**songs** - songs in music database |
| 43 | +- song_id, title, artist_id, year, duration |
| 44 | + |
| 45 | +4.**artists** - artists in music database |
| 46 | +- artist_id, name, location, latitude, longitude |
| 47 | + |
| 48 | +5.**time** - timestamps of records in songplays broken down into specific units |
| 49 | +- start_time, hour, day, week, month, year, weekday |
| 50 | + |
| 51 | + |
| 52 | +#### Project Template |
| 53 | +In addition to the data files, the project workspace includes six files: |
| 54 | + |
| 55 | +> 1.**test.ipynb** displays the first few rows of each table to let you check your database. |
| 56 | +> 2.**create_tables.py** drops and creates fact and dimension tables for the star schema in Redshift. |
| 57 | +> 3.**etl.py** load data from S3 into staging tables on Redshift and then process that data into your analytics tables on Redshift. |
| 58 | +> 4.**sql_queries.py** contains SQL statements, which will be imported into the two other files above. |
| 59 | +> 5.**README.md** provides discussion on your process and decisions for this ETL pipeline. |
| 60 | +
|
| 61 | + |
| 62 | +#### Project Steps |
| 63 | +##### Create Table Schemas |
| 64 | +> 1.Design schemas for your fact and dimension tables |
| 65 | +> 2.Write a SQL **CREATE** statement for each of these tables in **sql_queries.py** |
| 66 | +> 3.Complete the logic in **create_tables.py** to connect to the database and create these tables |
| 67 | +> 4.Write SQL **DROP** statements to drop tables in the beginning of **create_tables.py** if the tables already exist. This way, you can run **create_tables.py** whenever you want to reset your database and test your ETL pipeline. |
| 68 | +> 5.Launch a redshift cluster and create an IAM role that has read access to S3. |
| 69 | +> 6.Add redshift database and IAM role info to **dwh.cfg** |
| 70 | +> 7.Test by running **create_tables.py** and checking the table schemas in your redshift database. You can use Query Editor in the AWS Redshift console for this. |
| 71 | +
|
| 72 | +##### Build ETL Pipeline |
| 73 | +> 1.Implement the logic in **etl.py** to load data from S3 to staging tables on Redshift. |
| 74 | +> 2.Implement the logic in **etl.py** to load data from staging tables to analytics tables on Redshift. |
| 75 | +> 3.Test by running **etl.py** after running **create_tables.py** and running the analytic queries on your Redshift database to compare your results with the expected results. |
| 76 | +> 4.Delete your redshift cluster when finished. |
| 77 | +
|
| 78 | +The song play data model is as follows |
| 79 | + |
0 commit comments