with spark shell. Trying to clamp down on the INFO logging to console. Can't seem to solve it.
Since spark itself seems to add $SPARK_HOME/conf classpath (to verify what mahout ends up with in this case, run bin/mahout -spark classpath | sed 's/:/\n/g'), one obvious solution is to modify spark's conf/log4j.properties itself. When i do that, debug output is clamped down with spark shell, but not with Mahout's. I also did a hack and added log4j.properties into mahout's own classpath, to no avail either. So I can't seem to be able to track down this damn logger initialization issue, no matter what i do. it would seem Spark's elements of mahout shell start identically, but for some reason log4j just refuses to initialize differently. this INFO stuff coming from spark is quite annoying in the shell, we need to be able to regulate console output of the log4j. any help with the issue is appreciated. d
