Description
Task1: Data Exploration (4.5pts) 4.1.1 Task description You will explore the review dataset and write a program to answer the following questions: A. The total number of reviews (0.5pts) B. The number of reviews in a given year, y (1pts) C. The number of distinct users who have written the reviews (1pts) D. Top m users who have the largest number of reviews and its count (1pts) E. Top n frequent words in the review text. The words should be in lower cases. The following punctuations “(”, “[”, “,”, “.”, “!”, “?”, “:”, “;”, “]”, “)” and the given stopwords are excluded (1pts) 4.1.2 Execution commands Python: $ spark-submit task1.py Scala: $ spark-submit –class task1 hw1.jar Params: input_file – the input file (the review dataset) output_file – the output file contains your answers stopwords – the file contains the stopwords that should be removed for Question E y/m/n – see 4.1.1 4.1.3 Output format: You must write the results in the JSON format using exactly the same tags for each question (see an example in Figure 2). The answer for A/B/C is a number. The answer for D is a list of pairs [“user”, count]. The answer for E is a list of frequent words. All answers should be sorted by the count in the descending order. If two users/words have the same count, please sort them in the alphabetical order. 1 https://www.yelp.com/dataset Figure 2: An example output for task1 in JSON format 4.2 Task2: Exploration on Multiple Datasets (4pts) 4.2.1 Task description In task2, you will explore the two datasets together (i.e., review and business) and write a program to compute the average stars for each business category and output top n categories with the highest average stars. The business categories should be extracted from the “categories” tag in the business file and split by comma (also need to remove leading and trailing spaces for the extracted categories). You need to implement a version without Spark (2pts) and a version with Spark (2pts). You could then compare their performance yourself (not graded). 4.2.2 Execution commands Python: $ spark-submit task2.py Scala: $ spark-submit –class task2 hw1.jar Params: review _file – the input file (the review dataset) business_file – the input file (the business dataset) output_file – the output file contains your answers if_spark – either “spark” or “no_spark” n – top n categories with highest average stars (see 4.2.1) 4.2.3 Output format: You must write the results in the JSON format using exactly the same tags (see an example in Figure 3). The answer is a list of pairs [“category”, stars], which are sorted by the stars in the descending order. If two categories have the same value, please sort the categories in the alphabetical order. Figure 3: An example output for task2 in JSON format 4.3 Task3: Partition (4pts) 4.3.1 Task description In this task, you will learn how partitions work in the RDD. You need to compute the businesses that have more than n reviews in the review file. Other than the default way of partitioning the RDD, you should also design a customized partition function to improve the computational efficiency. Your program will be given the partition_type to decide which partition method to use. For eitherthe default or the customized partition function, you need to show the number of partitions for the RDD, the number of items per partition and the businesses that have more than n reviews(1ptsfor each partition type). Your customized partition function should improve the computational efficiency, i.e., reducing the time duration of execution (2pts). 4.3.2 Execution commands Python: $ spark-submit task3.py Scala: $ spark-submit –class task3 hw1.jar Params: input_file – the input file (the review dataset) output_file – the output file contains your answers partition_type – the partition function, either “default” or “customized” n_partitions – the number of partitions (only effective for the customized partition function) n – the threshold of the number of reviews (see 4.3.1) 4.3.3 Output format: You must write the results in the JSON format using exactly the same tags (see an example in Figure 4). The answer for the number of partitions is a number. The answer for the number of items per partition is a list of numbers. The answer for result is a list of pairs [“business”, count] (no need to sort). Figure 4: An example output for task3 in JSON format 5. About Vocareum 1. The purpose of Vocareum is for you to test if your code can be executed properly on Vocareum and can produce output in the correct format. It is your own responsibility to make sure your code could still produce correct result when the input dataset is modified. 2. You can use the provided datasets under the directory resource: /asnlib/publicdata/ (for Vocareum terminal: $ASNLIB/publicdata/) 3. You should upload the scripts under your workspace: work/ 4. Once you click on “Submit”, all your code is submitted, and submission script is automatically run on Vocareum. 5. You first test your scripts on your machine, and then on Voareum terminal, and then submit to Vocareum if the testing is successful. The submission script may not test all the aspects of your code, so you MUST test your code in the Vocareum terminal as well. 6. To test your Python/Scala implementations, you could use the required execution commands in the Vocareum terminal before submitting. 7. Here are the testing commands for your reference: 8. If you use python3, to test your code in the Vocareum terminal, remember to execute this command first: export PYSPARK_PYTHON=python3.6 9. You could add –driver-memory 4g –executor-memory 4g to your spark-submit command to limit its memory usage, in case your code could work properly in your local (with more resources) but would run into memory error during grading. 10. You will receive a submission report after Vocareum finishes executing your scripts. The submission report should include the running time and score of each task for the Python implementation. We do not test the Scala implementation during the submission period, but you could test your scala code on Vocareum. (eg. spark-submit –class task3 $ASNLIB/publicdata/review.json task3_default_ans default 20 50) 11. Vocareum will automatically run both Python and Scala implementations during the grading period. 12. Please start your assignment early! You can resubmit any script on Vocareum. We will grade on your last submission. 6. Grading Criteria (% penalty = % penalty of possible points you get) 1. You can use your free 5-day extension separately or together. You must submit a late-day request via https://forms.gle/4WZa1wYPv8FWmtQP7. This form is recording the number of late days you use for each assignment. By default, we will not count the late days if no request submitted. 2. There will be 10% bonus for each task (i.e., 0.45pts, 0.4pts, and 0.4pts) if your Scala implementations are correct. Only when your Python results are correct, the bonus of using Scala will be calculated. There is no partial point for Scala. 3. There will be no point if your submission cannot be executed on Vocareum. 4. There is no regrading. Once the grade is posted on the Blackboard, we will only regrade your assignments if there is a grading error. No exceptions. 5. There will be 20% penalty for the late submission within one week and no point after that. 6. If you use your late days, there wouldn’t be the 20% penalty but the final deadline wouldn’t be extended.
