[jira] [Resolved] (HBASE-5789) Offer the ability to delete a stale connection by using a configuration instead of HConnection

["stack (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/HBASE-5789?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

stack resolved HBASE-5789.
--------------------------
    Resolution: Not A Problem

Our Connection was redone for hbase 1.0. Resolving this issue as no longer a problem given we do not have stuff like delete a connection any more. Reopen if I have it wrong.

> Offer the ability to delete a stale connection by using a configuration instead of HConnection
> ----------------------------------------------------------------------------------------------
>
>                 Key: HBASE-5789
>                 URL: https://issues.apache.org/jira/browse/HBASE-5789
>             Project: HBase
>          Issue Type: Improvement
>    Affects Versions: 0.92.1
>            Reporter: Gilad Wolff
>
> The HConnectionManager offers a few methods to manage deletion of connections. The public deleteConnection method does not allow the caller to specify that the connection is stale. The deleteStaleConnection takes an HConnection instance. In order to get the HConnection instance a caller need to call getConnection with the connection's Configuration instance to retrieve the connection. But, getConnection will attempt to connect if the connection has already been deleted, which sort of defeat the purpose of deleting the connection. It also complicates caller as they need to handle ZooKeeperConnectionException. 
> To simplify clients it would be nice to be able to specify "staleConnection" on the deleteConnection method or offer a deleteStaleConnection method that takes a Configuration parameter. Or something completely different? 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)