I am just going to give you some design intents in the existing code.
as far as i can recollect, mahout context gives complete flexibility. You
can control the behavior but various degrees of overriding the default
behavior and doing more or less work on context setup on your own. (I
assume we are
I'm trying to refactor the Mahout dependency from the pom.xml of the Spark
interpreter (adding Mahout integration to Zeppelin)
Assuming MAHOUT_HOME is available, I see that the jars in source build live
in a different place than the jars in the binary distribution.
I'm to the point where I'm tryi
