[jira] Updated: (MAPREDUCE-2225) MultipleOutputs should not require the use of 'Writable'

["Harsh J Chouraria (JIRA)" <ji...@apache.org>]

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

Harsh J Chouraria updated MAPREDUCE-2225:
-----------------------------------------

    Attachment: multipleoutputs.nowritables.r1.diff

Attached a patch that removes Writable checks out of MultipleOutputs (In both mapred and mapreduce packages).

Ran the TestMultipleOutputs with successful results:
run-test-mapred-all-withtestcaseonly:
    [mkdir] Created dir: /home/hack/projects/work/MapReduce/build/test/data
    [mkdir] Created dir: /home/hack/projects/work/MapReduce/build/test/logs
     [copy] Copying 1 file to /home/hack/projects/work/MapReduce/build/test/extraconf
     [copy] Copying 1 file to /home/hack/projects/work/MapReduce/build/test/extraconf
    [junit] WARNING: multiple versions of ant detected in path for junit 
    [junit]          jar:file:/usr/share/java/apache-ant/lib/ant.jar!/org/apache/tools/ant/Project.class
    [junit]      and jar:file:/home/hack/.ivy2/cache/ant/ant/jars/ant-1.6.5.jar!/org/apache/tools/ant/Project.class
    [junit] Running org.apache.hadoop.mapred.lib.TestMultipleOutputs
    [junit] Tests run: 2, Failures: 0, Errors: 0, Time elapsed: 3.52 sec

> MultipleOutputs should not require the use of 'Writable'
> --------------------------------------------------------
>
>                 Key: MAPREDUCE-2225
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-2225
>             Project: Hadoop Map/Reduce
>          Issue Type: Improvement
>          Components: job submission
>    Affects Versions: 0.20.1
>            Reporter: Harsh J Chouraria
>            Assignee: Harsh J Chouraria
>             Fix For: 0.23.0
>
>         Attachments: multipleoutputs.nowritables.r1.diff
>
>   Original Estimate: 0.02h
>  Remaining Estimate: 0.02h
>
> MultipleOutputs right now requires for Key/Value classes to utilize the Writable and WritableComparable interfaces, and fails if the associated key/value classes aren't doing so.
> With support for alternates like Avro serialization, using Writables isn't necessary and thus the MO class must not strictly check for them.
> And since comparators may be given separately, key class doesn't need to be checked for implementing a comparable (although it is good design if the key class does implement Comparable at least).
> Am not sure if this brings about an incompatible change (does Java have BIC? No idea).

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