1) you should run zinc incremental compiler 2) if you want breakpoints that should likely be done in local mode 3) adjust the log4j.properties settings and you can start to see the logInfo
2015-12-27 0:20 GMT-08:00 salexln <sale...@gmail.com>: > Hi guys, > > I'm debugging my code in mllib/clustering but i'm not sure i'm doing it the > best way: > I build my changes in mllib using "build/mvn -DskipTests package" and then > running invoking my code using > "./bin/spark-shell" > > My two main issues: > 1) After each change the build (build/mvn -DskipTests package) takes ~15 > mins > 2) I cannot put breakpoints > 3) If I add println of logInfo, I do not see it in the console. > > What us the best way to debug it? > > > > > -- > View this message in context: > http://apache-spark-developers-list.1001551.n3.nabble.com/what-is-the-best-way-to-debug-spark-mllib-tp15809.html > Sent from the Apache Spark Developers List mailing list archive at > Nabble.com. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@spark.apache.org > For additional commands, e-mail: dev-h...@spark.apache.org > >
