[
https://issues.apache.org/jira/browse/MAHOUT-1685?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14492498#comment-14492498
]
Pat Ferrel commented on MAHOUT-1685:
------------------------------------
If you read between the lines of Sean's reply, he is saying none of it is meant
to be a supported "API". Which I take to mean they give no indication of change
or deprecation (rather obvious). They have no intent to make it public again so
If we don't work around we'll have to petition for a supported API.
Some obvious solutions, without looking too deeply:
1) create our own shell from the Scala REPL, maybe using the Spark's shell as a
template. Pro is we depend on Scala REPL + Spark supported APIS. Downside is
that this is a much bigger chunk of code than current shell.
2) Can we turn the shell into a .mscala type scala-as-script extension to the
Spark shell? This would obviously require a lot of imports and the compile
delay at every load. Upside is that it goes through supported APIs that are
less likely to change. Downside is little control over initialization of the
context and kryo.
3) Petition them to support the API we use. This is by far the easiest and
seems like it might be worth writing a Jira in Spark if only to get their
response.
> Move Mahout shell to Spark 1.3+
> -------------------------------
>
> Key: MAHOUT-1685
> URL: https://issues.apache.org/jira/browse/MAHOUT-1685
> Project: Mahout
> Issue Type: Improvement
> Components: Mahout spark shell
> Reporter: Pat Ferrel
> Assignee: Dmitriy Lyubimov
> Priority: Critical
> Fix For: 0.11.0
>
> Attachments: mahout-shell-spark-1.3-errors.txt
>
>
> Building for Spark 1.3 we found several important APIS used by the shell are
> now marked package private in Spark, making them inaccessible.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
