[
https://issues.apache.org/jira/browse/MAHOUT-1500?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14059183#comment-14059183
]
ASF GitHub Bot commented on MAHOUT-1500:
----------------------------------------
Github user pferrel commented on the pull request:
https://github.com/apache/mahout/pull/21#issuecomment-48767998
So you don't see how changing the drm API or storage format will now break
code in two places written for two different engines? If I make the change to
drm I can fix spark breakage but not h2o. This bit of code is extremely stable
and super simple for spark so may be a bad example but new code will not be so
stable just the opposite. For each new IO operation (SparkContext dependent)
or engine tuning (SparkConf dependent) we will grow the problem. The core will
become untouchable or breakage will happen in places one engineer will not be
able to fix.
This is a real issue, I need to change code in math-scala today, already
have but it isn't pushed. Who knows what that will break in h2o
implementations? I will be changing cooccurrence tests, so have to make them in
two places. Maybe I can do that but when they diverge further than this example
I won't be able to.
You guys need to address these issues as if you were supporting two engines
for all Mahout code or you will never see what Mahout committers problems will
be.
> H2O integration
> ---------------
>
> Key: MAHOUT-1500
> URL: https://issues.apache.org/jira/browse/MAHOUT-1500
> Project: Mahout
> Issue Type: Improvement
> Reporter: Anand Avati
> Fix For: 1.0
>
>
> Provide H2O backend for the Mahout DSL
--
This message was sent by Atlassian JIRA
(v6.2#6252)
