You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "stack (JIRA)" <ji...@apache.org> on 2011/06/29 05:41:28 UTC

[jira] [Commented] (HBASE-4039) Users should be able to choose custom TableInputFormats without modifying TableMapReduceUtil.initTableMapperJob().

    [ https://issues.apache.org/jira/browse/HBASE-4039?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13056975#comment-13056975 ] 

stack commented on HBASE-4039:
------------------------------

Do you have a patch for us Edward?

> Users should be able to choose custom TableInputFormats without modifying TableMapReduceUtil.initTableMapperJob().
> ------------------------------------------------------------------------------------------------------------------
>
>                 Key: HBASE-4039
>                 URL: https://issues.apache.org/jira/browse/HBASE-4039
>             Project: HBase
>          Issue Type: New Feature
>          Components: mapreduce
>    Affects Versions: 0.90.3
>         Environment: HBase-0.90.3. OS, hardware specs not relevant.
>            Reporter: Edward Choi
>            Priority: Minor
>
> Currently, org.apache.hadoop.hbase.mapreduce.TableMapReduceUtil.initTableMapperJob() forces any Hbase job to use the default TableInputFormat.class as the job's input format class.
> "job.setInputFormatClass(TableInputFormat.class);" ==> This line is included in initTableMapperJob().
> This restriction causes users to modify initTableMapperJob() in addition to implementing their own TableInputFormat. 
> It would be nicer if users can use custom TableInputFormats without additionally tampering with HBase source code.

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