1 / 9

Introduction to Git and Discussion on assignment 1

Gang Luo Sept. 14, 2010. Introduction to Git and Discussion on assignment 1. Git. Source code management Version control Enable team collaboration One central repository, multiple local copies Synchronize local copy with the central one to ensure everybody see the latest modification.

chaela
Download Presentation

Introduction to Git and Discussion on assignment 1

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Gang Luo Sept. 14, 2010 Introduction to GitandDiscussion on assignment 1

  2. Git • Source code management • Version control • Enable team collaboration • One central repository, multiple local copies • Synchronize local copy with the central one to ensure everybody see the latest modification You should access the central repository from linux.cs.duke.edu, instead of hadoop21.cs.duke.edu

  3. Before we start • Install Git • PuTTY + Git (for windows) • Eclipse + EGit (for windows/Linux) • linux.cs.duke.edu (Git already installed ) • apt-get install git-core (for Ubuntu Linux) • yum install git-core (for Federa/Other Linux) • Initilization • Set user name, email and color to highlight something • Clone • Localize a copy of remote repository • git clone ssh://USERNAME@linux.cs.duke.edu/usr/research/proj/git/cps216/USERNAME.git

  4. Using Git • Adding files • git add . (don’t forget the dot which means all) • Commit changes • git commit –m “message” –a • “message” could be anything you want to appear in the log • Synchronize with remote repository • git push • Push your modification to the central repository • git pull • Update your local copy from the central repository

  5. Convention for you submission • Put you code in the appropriate directories • e.g. cps216/assignemnt1/parta • Give README file • Briefly shows the organization of your code, the meaning of each class and instructions on how to run your code

  6. Demo Time

  7. Some issues for assignment 1 • Output key/value type setting • setOutputValueClass() and setOutputKeyClass() cover both map and reduce output key/value type. • What if your mapper output types are different from reducer? • Specify map input/output by setMapOutputValueClass() and/or setMapOutputKeyClass()

  8. Some issues for assignment 1 • Input/output types for combiner • Input types should be the same as map output types. (Obviously) • Output types should be also the same as map output types. (why?) • Combiner is not called on every record. If you have a different output types in combiner, you will end up with having two different types at reducer. (K1, V1) → (K2, V2) → (K2, V2) → (K2, V2) → (K2, V2) → (K3, V3) Mapper Combiner Reducer

  9. Some issues for assignment 1 • Separate a string by separator “|” • If “|” doesn't work, try “\\|” • Need to ship more than one value in one value object? • Implement you own Writable type, or • Use Text. “23#16#87” contains three values in one string! • configure(JobConf conf) • Put your initialization in this method • Good place to retrieve some parameters from JobConf. ( conf.getXXX() )

More Related