If I understand correctly, mrlegacy should remain, just hdfs/non-mr stuff extracted into separate module, for reuse in math-scala and mahout-spark module, so they do not depend on mrlegacy?
Maybe we should rename mrlegacy to mahout-mr or mahout-mapred or mahout-mapreduce. Legacy, if kept in master branch doesn't mean anything. Kind regards, Stevo Slavic. On Tue, Mar 24, 2015 at 9:30 PM, Pat Ferrel (JIRA) <[email protected]> wrote: > > [ > https://issues.apache.org/jira/browse/MAHOUT-1655?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14378530#comment-14378530 > ] > > Pat Ferrel commented on MAHOUT-1655: > ------------------------------------ > > We can work together if you want to start a "MAHOUT-1655" branch on your > personal github repo. > > > Refactor module dependencies > > ---------------------------- > > > > Key: MAHOUT-1655 > > URL: https://issues.apache.org/jira/browse/MAHOUT-1655 > > Project: Mahout > > Issue Type: Improvement > > Components: mrlegacy > > Reporter: Pat Ferrel > > Assignee: Andrew Musselman > > Priority: Critical > > Fix For: 0.10.0 > > > > > > Make a new module, call it mahout-hadoop. Move anything there that is > currently in mrlegacy but used in math-scala or spark. Remove dependencies > on mrlegacy altogether if possible by using other core classes. > > The goal is to have math-scala and spark module depend on math, and a > small module called mahout-hadoop (much smaller than mrlegacy). > > > > -- > This message was sent by Atlassian JIRA > (v6.3.4#6332) >
