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 Thu, 16 Apr 2015 08:34:59 GMT

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

Mikhail Antonov commented on HBASE-13349:
-----------------------------------------

Hm. What do you think regarding removing managed connections in 1.2? Something to consider,
or safer to not do that until 2.0?

If former, I'd say we could just leave current handling code in place.

on that - 

bq. Is that really necessary, i.e can we create Tables and Admins with a managed connection?


I'd be for the option when we do throw an exception. Allowing creation of Tables and Admins
on managed connections (not thinking for the moment of how to implement it technically) would,
IMO, encourage folks to continue using them?

> 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
(v6.3.4#6332)

Mime
View raw message