[
https://issues.apache.org/jira/browse/MAHOUT-1529?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14017105#comment-14017105
]
Ted Dunning commented on MAHOUT-1529:
-------------------------------------
I am not sold but I don't think it is germane to this bug. I think that the
details of whether it is exactly done with common inheritance or standardized
traits is an open question, but I think that the overall push that we need some
common characteristics that can be communicated easily to the person writing
code is very important.
We also need to support some things that are very inefficient for cases where
it just needs to be done. It is easy to come up with scenarios like diagnostic
systems that need to get the value of a single cell and damn the cost. That
doesn't make element by element access a primary idiom. It just means that it
is possible to do.
> 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
> Assignee: 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-
> (6) Stratosphere/Flink conceptual api changes.
> *Current tracker:* PR #1 https://github.com/apache/mahout/pull/1 - closed,
> need new PR for remaining things once ready.
> *Pull requests are welcome*.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
