[jira] [Updated] (MAHOUT-664) Remove usage of XStream string serialization too?

["Sean Owen (JIRA)" <ji...@apache.org>]

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

Sean Owen updated MAHOUT-664:
-----------------------------

         Due Date: 30/Jun/11
    Fix Version/s:     (was: 1.0)
                   0.6
         Assignee: Sean Owen

> Remove usage of XStream string serialization too?
> -------------------------------------------------
>
>                 Key: MAHOUT-664
>                 URL: https://issues.apache.org/jira/browse/MAHOUT-664
>             Project: Mahout
>          Issue Type: Improvement
>    Affects Versions: 0.4, 0.5
>            Reporter: Sean Owen
>            Assignee: Sean Owen
>            Priority: Minor
>             Fix For: 0.6
>
>
> In the spirit of MAHOUT-510 and continuing to standardize approaches without going too nuts -- I notice that there is only one use of XStream left in the code, in StringUtils, which is merely a wrapper for serializing/deserializing an object to a String.
> There are two key mahout-core usages:
> - org.apache.mahout.ga.watchmaker. Here it seems to be used to serialize/deserialize a candidate solution to a file on HDFS and fed into a mapper. Surely it's more appropriate to do something with Writable here?
> - org.apache.mahout.df.mapreduce. It's used to serialize/deserialize a DefaultTreeBuilder. Does it need to be done? it seems like DefaultTreeBuilder is parameterized entirely by its param "m" but I haven't looked hard.
> All of the other usages are in mahout-examples/, which suggests they're of secondary importance.
> Some usages are serialization of longs and char[], which seems pointless.
> Any thoughts? putting this on the map for 1.0.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira