hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Nick Dimiduk (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-13349) Reduce NeedUnmanagedConnectionException issues
Date Wed, 15 Apr 2015 22:02:59 GMT

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

Nick Dimiduk commented on HBASE-13349:

I'm open to suggestions here. It's about correct object lifecycle management, right? How can
we avoid creep in API surface area?

> Reduce NeedUnmanagedConnectionException issues
> ----------------------------------------------
>                 Key: HBASE-13349
>                 URL: https://issues.apache.org/jira/browse/HBASE-13349
>             Project: HBase
>          Issue Type: Bug
>    Affects Versions: 1.0.0
>            Reporter: Solomon Duskis
>             Fix For: 1.1.0
> Managed connections are a bit of a pain when it comes to the new API.  If a connection
is managed, then connection.getAdmin() and connection.getTable(..) throw NeedUnmanagedConnectionException.
 Is that really necessary, i.e can we create Tables and Admins with a managed connection?
 If not, can we come up with something better than sprinkling NeedUnmanagedConnectionException
try-catch blocks in the HBase code base to fix this problem?

This message was sent by Atlassian JIRA

View raw message