The map-reduce programming paradigm is a fundamental tool used in processing large data sets, and is supported in current tools such as Hadoop and MongoDB. In this course you will gain an understanding of the concepts embodied in map-reduce, and will investigate how map-reduce is used to address various problems in processing and analyzing large data sets. This course will explore map-reduce as implemented in Hadoop, as well as the associated distributed file system (HDFS). This course will also survey some of the tools built on top of Hadoop and HDFS. |
  |
Upon completing this course, the student will be able to write map-reduce programs for various large data set processing tasks, and understand how various tools in the Hadoop ecosystem utilize map-reduce and the Hadoop distributed file system (HDFS). |
  |
Data structures, Java programming experience. |
  |
|
  |
David Franke
|
  |
Swadhin Pradhan
|
  |
Assignment # | ||||
---|---|---|---|---|
Date | Given | Due | Points | Reading |
Aug. 28 | Dean, Ghemawat paper | |||
Sep. 2 | 1 | Design Patterns, Ch. 1 | ||
Sep. 4 | ||||
Sep. 9 | 2 | 1 | 10 | Design Patterns, Ch. 2 |
Sep. 11 | ||||
Sep. 16 | 3 | 2 | 15 | |
Sep. 18 | ||||
Sep. 23 | 4 | 3 | 15 | |
Sep. 25 | ||||
Sep. 30 | 5 | 4 | 20 | Design Patterns, Ch. 4 |
Oct. 2 | ||||
Oct. 7 | 6 | 5 | 10 | |
Oct. 9 | ||||
Oct. 14 | ||||
Oct. 16 | 7 | 6 | 20 | Design Patterns, Ch. 5 |
Oct. 21 | ||||
Oct. 23 | ||||
Oct. 28 | 8 | 7 | 25 | |
Oct. 30 | ||||
Nov. 4 | ||||
Nov. 6 | 9 | 8 | 25 | Design Patterns, Ch. 3 |
Nov. 11 | ||||
Nov. 13 | 10 | 9 | 10 | Design Patterns, Ch. 6 |
Nov. 18 | ||||
Nov. 20 | 11 | 10 | 15 | |
Nov. 25 | Design Patterns, Ch. 7 | |||
Nov. 27 (Holiday) | ||||
Dec. 2 | 12 | 11 | 15 | Design Patterns, Ch. 8 |
Dec. 4 | ||||
Dec. 10 | 12 | 20 | Not a class day |
This course will focus on writing code to solve various problems, so assignments will be programming assignments. These programs will be cumulative in that subsequent assignments will build on previous programs you have written, so it is important to complete assignments on time so you can move on to the next assignment. Small datasets will be provided for each assignment so that you will not consume too much computing resource (time and space) while developing your solution. Some assignments will also offer a large dataset so that you can measure how your map-reduce solution scales with the dataset size and the computing resources available. You are free to discuss approaches to solving the assigned problems with your classmates, but each student is expected to write their own code. Source code must be submitted for each assignment, in addition to the results you obtained when running your program against the datasets provided. If duplicate work is detected, all parties involved will be penalized. All students should read and be familiar with the UTCS Rules to Live By.
Grading Rubric:
Late PolicyRequired artifacts for each programming assignment are due at the start of class (9:30 AM) on the due date, as we will be discussing the solution during that class period. Penalty for late submission is 25%. Special Notes on Assignment Submission and Grading:
|
  |
Further Reading
|