hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mikhail Antonov (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-13349) Reduce NeedUnmanagedConnectionException issues
Date Fri, 27 Mar 2015 19:39:53 GMT

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

Mikhail Antonov commented on HBASE-13349:

Which fix release you have in mind for this issue [~sduskis]? I believe managed connections
are going to be removed in master (and 2.0), not yet sure it's feasible for 1.1 (technically
that might be backward-compatible thing), hence this very exception class could be just removed.
In fact, I removed this in a patch to the jira I linked.

> Reduce NeedUnmanagedConnectionException issues
> ----------------------------------------------
>                 Key: HBASE-13349
>                 URL: https://issues.apache.org/jira/browse/HBASE-13349
>             Project: HBase
>          Issue Type: Bug
>            Reporter: Solomon Duskis
> 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