hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Solomon Duskis (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HBASE-12798) Map Reduce jobs should not create Tables in setConf()
Date Fri, 02 Jan 2015 15:27:13 GMT

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

Solomon Duskis updated HBASE-12798:
-----------------------------------
    Description: 
setConf() gets called in many places along the Map/Reduce chain.  HBase creates Tables and
etc in setConf in a few places.  There should be a better place to create the Table, often
while creating a TableRecordReader.

This issue will tackle the following classes:
- TableOutputFormatBase
- TableInputFormatBase

Other classes that could use a look over:
- HRegionPartitioner
- ReplicationLogCleaner
-TableInputFormatBase (this requires changing documentation and further thought about how
users ought to close connections)

  was:
setConf() gets called in many places along the Map/Reduce chain.  HBase creates Tables and
etc in setConf in a few places.  There should be a better place to create the Table, often
while creating a TableRecordReader.

This issue will tackle the following classes:
- TableOutputFormatBase

Other classes that could use a look over:
- HRegionPartitioner
- ReplicationLogCleaner
-TableInputFormatBase (this requires changing documentation and further thought about how
users ought to close connections)


> Map Reduce jobs should not create Tables in setConf()
> -----------------------------------------------------
>
>                 Key: HBASE-12798
>                 URL: https://issues.apache.org/jira/browse/HBASE-12798
>             Project: HBase
>          Issue Type: Bug
>            Reporter: Solomon Duskis
>            Assignee: Solomon Duskis
>             Fix For: 1.0.0, 2.0.0
>
>
> setConf() gets called in many places along the Map/Reduce chain.  HBase creates Tables
and etc in setConf in a few places.  There should be a better place to create the Table, often
while creating a TableRecordReader.
> This issue will tackle the following classes:
> - TableOutputFormatBase
> - TableInputFormatBase
> Other classes that could use a look over:
> - HRegionPartitioner
> - ReplicationLogCleaner
> -TableInputFormatBase (this requires changing documentation and further thought about
how users ought to close connections)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message