[
https://issues.apache.org/jira/browse/HBASE-4039?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13056995#comment-13056995
]
Edward Choi commented on HBASE-4039:
------------------------------------
I haven't created a patch. This is the first time I've created an issue in jira.
I didn't know I was supposed to also prepare a corresponding patch.
I could make a patch, but I would have to learn how to do it. (I know there's a
guideline in Hadoop wiki)
Would it be better to shut down the issue until I have a working patch?
> 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
