[
https://issues.apache.org/jira/browse/MAHOUT-1894?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15855010#comment-15855010
]
ASF GitHub Bot commented on MAHOUT-1894:
----------------------------------------
Github user rawkintrevo commented on the issue:
https://github.com/apache/mahout/pull/271
@skanjila the shell is useful enough that I'd like to keep it around if
possible. Some reasons off the cuff:
- Good for 'demo-ing' mahout. Fire up the shell do some simple stuff.
- Good for sanity checking bugs in Zeppelin (something very close to my
heart)
- As we move to add algorithms, I envision Mahout being used for more
interactive data science. In that world there is a lot of iterative "try this,
see what happens, try that" kind of approach. I do most of that in Zeppelin,
but some people may use JetBrains/ other IDEs and the shell is useful in these
cases.
To your point- yes, 86ing the entire shell module certainly poses some very
attractive advantages. What we're seeing in this PR is an opportunity to get
best of both worlds (no code, but still have a shell). Just need to work out
some kinks on getting it working with spark-shell correctly.
> Add support for Spark 2x backend
> --------------------------------
>
> Key: MAHOUT-1894
> URL: https://issues.apache.org/jira/browse/MAHOUT-1894
> Project: Mahout
> Issue Type: Task
> Components: spark
> Affects Versions: 0.13.0
> Reporter: Suneel Marthi
> Assignee: Trevor Grant
> Priority: Critical
> Fix For: 1.0.0, 0.13.0, 0.14.0
>
>
> add support for Spark 2.x as backend execution engine.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
