[
https://issues.apache.org/jira/browse/HBASE-3578?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13000454#comment-13000454
]
Dan Harvey commented on HBASE-3578:
-----------------------------------
Thanks that should be fine, it's not a critical issue just will make things
cleaner to work with.
For us as I didn't want to use a patched version of HBase in production with
upgrading to 0.90 I've modified all our jobs to configure things as needed, but
it would be great if we didn't have to do this all the time.
> TableInputFormat does not setup the configuration for HBase mapreduce jobs
> correctly
> ------------------------------------------------------------------------------------
>
> Key: HBASE-3578
> URL: https://issues.apache.org/jira/browse/HBASE-3578
> Project: HBase
> Issue Type: Bug
> Components: mapreduce
> Affects Versions: 0.90.0, 0.90.1
> Reporter: Dan Harvey
> Assignee: Dan Harvey
> Fix For: 0.92.0
>
> Attachments: mapreduce_configuration.patch
>
>
> In 0.20.x and earlier TableMapReduceUtil (and other Input/OutputFormat
> classes) used to setup the HTable with a HBaseConfiguration object, now that
> has been deprecated in #HBASE-2036 they are constructed with Hadoop
> configuration objects which do not contain the configuration xml file
> resources required to setup HBase. I think it is currently expected this is
> done when constructing the job but as this needs to be done for every HBase
> mapreduce job it would be cleaner if the TableMapReduceUtil class did this
> whilst setting up the TableInput/OutputFormat classes.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
