From ca8c5dedea7907cf26ec63309f4e99030e644351 Mon Sep 17 00:00:00 2001 From: Bryan Newbold Date: Mon, 21 May 2018 11:59:14 -0700 Subject: success running with com.twitter.scalding.Tool --- jvm-mapreduce/learning.txt | 9 +++++++++ 1 file changed, 9 insertions(+) (limited to 'jvm-mapreduce/learning.txt') diff --git a/jvm-mapreduce/learning.txt b/jvm-mapreduce/learning.txt index 1fe64bd..6fe1442 100644 --- a/jvm-mapreduce/learning.txt +++ b/jvm-mapreduce/learning.txt @@ -12,6 +12,15 @@ Or, with actual files on hadoop: Horray! One issue with this was that building scalding took *forever* (meaning 30+ minutes). +potentially instead: + + hadoop jar scald-mvp-assembly-0.1.0-SNAPSHOT.jar com.twitter.scalding.Tool main.scala.example.WordCountJob --hdfs --input hdfs:///user/bnewbold/dummy.txt --output hdfs:///user/bnewbold/test_scalding_out2 + +Hypothesis: class name should be same as file name. Don't need `main` function +if using Scalding Tool wrapper jar. Don't need scald.rb. + + hadoop jar scald-mvp-assembly-0.1.0-SNAPSHOT.jar com.twitter.scalding.Tool example.WordCount --hdfs --input hdfs:///user/bnewbold/dummy.txt --output hdfs:///user/bnewbold/test_scalding_out2 + ## sbt Uncommenting this line in scalding:build.sbt sped things way up (don't need to -- cgit v1.2.3