Mailing-List: contact mapreduce-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: mapreduce-issues@hadoop.apache.org
Date: Mon, 28 Feb 2011 17:50:37 +0000 (UTC)
From: "Harsh J Chouraria (JIRA)" <jira@apache.org>
To: mapreduce-issues@hadoop.apache.org
Message-ID: 
 <128110215.2234.1298915437185.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: <9199842.205151292778482449.JavaMail.jira@thor>
Subject: [jira] Updated: (MAPREDUCE-2225) MultipleOutputs should not require
 the use of 'Writable'
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ 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.r2.diff

Sure, it should avoid a raw types warning I  think? Here's a patch for that update.

> 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
>         Environment: Linux
>            Reporter: Harsh J Chouraria
>            Assignee: Harsh J Chouraria
>            Priority: Blocker
>             Fix For: 0.22.0
>
>         Attachments: multipleoutputs.nowritables.r1.diff, multipleoutputs.nowritables.r2.diff, multipleoutputs.nowritables.r2.diff
>
>   Original Estimate: 1m
>  Remaining Estimate: 1m
>
> 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.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira