[
https://issues.apache.org/jira/browse/HBASE-4039?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brock Noland updated HBASE-4039:
--------------------------------
Attachment: HBASE-4039.1.patch
1) The attached patch adds an InputFormat as an optional parameter to
initTableMapper.
2) Would it be possible to do this without via
TableMapReduceUtil.initTableMapper(...job)
job.setInputFormat(...)
TableMapReduceUtil.addDependencyJars(..)
Not sure, just a thought.
> 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
> Attachments: HBASE-4039.1.patch
>
>
> 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
