Github user Leemoonsoo commented on the issue:
https://github.com/apache/incubator-zeppelin/pull/928
I think whether creating mahout interpreter or not will be depends on
expectation that how user uses mahout.
If usecase is let spark user uses mahout during their work along with all
the other libraries, it make sense to load mahout as a library.
But if usecase is more like mahout user leverages spark, flink, etc as a
execution engine to run mahout algorithms and more tight integration between
Zeppelin and Mahout required in the future, then creating an interpreter more
make sense.
@rawkintrevo What do you think?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
