[
https://issues.apache.org/jira/browse/MAHOUT-1529?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13988516#comment-13988516
]
Dmitriy Lyubimov edited comment on MAHOUT-1529 at 5/3/14 1:30 AM:
------------------------------------------------------------------
it is expensive for anybody's time (compared to REPL adaptation). I certainly
won't try to do it at this point. If you want to do it, yes, please file a new
jira.
Also, REPL cannot be used with mahout as is. So yes, it is well warranted what
we did.
I am not sure about re-branding, we did too little to warrant that indeed, but
REPL can't work with Mahout, or at the very least it is awkward to do so
manually (i.e. tracing all mahout jar dependencies, add them to session and
make sure all proper imports are done).
was (Author: dlyubimov):
it is expensive for anybody's time. I certainly won't try to do it at this
point. If you want to do it, yes, please file a new jira.
> Finalize abstraction of distributed logical plans from backend operations
> -------------------------------------------------------------------------
>
> Key: MAHOUT-1529
> URL: https://issues.apache.org/jira/browse/MAHOUT-1529
> Project: Mahout
> Issue Type: Improvement
> Reporter: Dmitriy Lyubimov
> Fix For: 1.0
>
>
> We have a few situations when algorithm-facing API has Spark dependencies
> creeping in.
> In particular, we know of the following cases:
> (1) checkpoint() accepts Spark constant StorageLevel directly;
> (2) certain things in CheckpointedDRM;
> (3) drmParallelize etc. routines in the "drm" and "sparkbindings" package.
> (5) drmBroadcast returns a Spark-specific Broadcast object
> *Current tracker:*
> https://github.com/dlyubimov/mahout-commits/tree/MAHOUT-1529.
> *Pull requests are welcome*.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
