Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Tue, 23 Oct 2012 10:37:12 +0000 (UTC)
From: "Dave Beech (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: <1893745281.15269.1350988632413.JavaMail.jiratomcat@arcas>
In-Reply-To: <2141886034.10137.1350921012145.JavaMail.jiratomcat@arcas>
Subject: [jira] [Updated] (HBASE-7024) TableMapReduceUtil.initTableMapperJob
 unnecessarily limits the types of outputKeyClass and outputValueClass
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Dave Beech updated HBASE-7024:
------------------------------

    Attachment: HBASE-7024.patch

OK, thanks. Can I propose this patch - it simply removes the "extends Writable/WritableConfigurable" bit from the outputKeyClass and outputValueClass parameters
                
> TableMapReduceUtil.initTableMapperJob unnecessarily limits the types of outputKeyClass and outputValueClass
> -----------------------------------------------------------------------------------------------------------
>
>                 Key: HBASE-7024
>                 URL: https://issues.apache.org/jira/browse/HBASE-7024
>             Project: HBase
>          Issue Type: Bug
>          Components: mapreduce
>            Reporter: Dave Beech
>            Priority: Minor
>         Attachments: HBASE-7024.patch
>
>
> The various initTableMapperJob methods in TableMapReduceUtil take outputKeyClass and outputValueClass parameters which need to extend WritableComparable and Writable respectively. 
> Because of this, it is not convenient to use an alternative serialization like Avro. (I wanted to set these parameters to AvroKey and AvroValue). 
> The methods in the MapReduce API to set map output key and value types do not impose this restriction, so is there a reason to do it here?

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira