You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@hbase.apache.org by "Jan Lukavsky (JIRA)" <ji...@apache.org> on 2011/08/29 18:14:37 UTC

[jira] [Updated] (HBASE-3578) TableInputFormat does not setup the configuration for HBase mapreduce jobs correctly

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

Jan Lukavsky updated HBASE-3578:
--------------------------------

    Attachment: HBASE-3578.patch

> 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: HBASE-3578.patch, 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