[
https://issues.apache.org/jira/browse/HBASE-13027?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sean Busbey updated HBASE-13027:
--------------------------------
Fix Version/s: 2.0.0
adding 2.0.0 fix version back in, since we are changing behavior on master.
setHTable will now result in creating a new Connection if the HTable's backing
Connection is managed. The implementations we ship in 2.y don't use managed
connection behind HTables, but a user could still assemble one.
> mapreduce.TableInputFormatBase should create its own Connection if needed
> -------------------------------------------------------------------------
>
> Key: HBASE-13027
> URL: https://issues.apache.org/jira/browse/HBASE-13027
> Project: HBase
> Issue Type: Bug
> Components: mapreduce
> Affects Versions: 1.0.0, 1.1.0
> Reporter: Sean Busbey
> Assignee: Sean Busbey
> Priority: Blocker
> Labels: hive
> Fix For: 1.0.0, 2.0.0, 1.1.0
>
>
> Folks extending the mapreduce.TableInputFormatBase class and relying on the
> 0.98 way of doing table initialization (as given in the example in the
> javadoc) will currently always get an error.
> When taking in a HTable, the current implementation retrieves a Connection
> instance from the table and then an Admin instance from said Connection. The
> getAdmin call validates that it only is called on unmanaged connections, but
> when folks construct an HTable instance according to the examples, it ends up
> backed by a managed connection.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
