hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sean Busbey (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-13027) mapreduce.TableInputFormatBase should create its own Connection if needed
Date Fri, 13 Feb 2015 15:36:11 GMT

    [ https://issues.apache.org/jira/browse/HBASE-13027?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14320303#comment-14320303
] 

Sean Busbey commented on HBASE-13027:
-------------------------------------

failing tests are unrelated. That remaining javadoc warning is HBASE-13038.

Any other concerns [~enis]?

> 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
>
>         Attachments: HBASE-13027-0.98.1.patch.txt, HBASE-13027.1.patch.txt, HBASE-13027.2.patch.txt,
HBASE-13027.3.patch.txt
>
>
> 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)

Mime
View raw message