[jira] Resolved: (MAHOUT-205) Pull Writable (and anything else hadoop dependent) out of the matrix module

["Jake Mannix (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/MAHOUT-205?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jake Mannix resolved MAHOUT-205.
--------------------------------

    Resolution: Fixed

committed in revision 898669

> Pull Writable (and anything else hadoop dependent) out of the matrix module
> ---------------------------------------------------------------------------
>
>                 Key: MAHOUT-205
>                 URL: https://issues.apache.org/jira/browse/MAHOUT-205
>             Project: Mahout
>          Issue Type: Improvement
>          Components: Math
>    Affects Versions: 0.1
>         Environment: all
>            Reporter: Jake Mannix
>            Assignee: Jake Mannix
>            Priority: Minor
>             Fix For: 0.3
>
>         Attachments: MAHOUT-205.patch, MAHOUT-205.patch, MAHOUT-205.patch
>
>
> Vector and Matrix extend Writable, and while that was merely poorly coupled before, it will be an actual problem now that we have a separate submodule for matrix: this module should not depend on hadoop at all, ideally.   Distributed matrix work, as well as simply Writable wrappers can go somewhere else (where?  core?  yet another submodule which depends on matrix?), but it would be really nice if we could produce an artifact which doesn't require Hadoop which has our core linear primitives.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.