hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Enis Soztutar (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-14296) ConnectionManager should validate the table existence before returning the table instance
Date Tue, 25 Aug 2015 18:40:45 GMT

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

Enis Soztutar commented on HBASE-14296:
---------------------------------------

bq. I was thinking about adding a exist() before returning a table instance but it will be
a RPC call.
I think this is too expensive. In most of the cases getTable() should be relatively cheap,
we even cache the configuration options via TableConfiguration object to not to pay the parsing
cost in Table instantiation. The clients can very easily wrap the call in an Admin.exists()
if they are interested. 

> ConnectionManager should validate the table existence before returning the table instance
> -----------------------------------------------------------------------------------------
>
>                 Key: HBASE-14296
>                 URL: https://issues.apache.org/jira/browse/HBASE-14296
>             Project: HBase
>          Issue Type: Bug
>          Components: Client
>    Affects Versions: 2.0.0, 1.2.0, 0.98.15
>            Reporter: Pankaj Kumar
>            Assignee: Pankaj Kumar
>            Priority: Minor
>
> Table instance should be returned only when table exist.
> {code}
>     public HTableInterface getTable(TableName tableName, ExecutorService pool) throws
IOException {
>       if (managed) {
>         throw new NeedUnmanagedConnectionException();
>       }
>       return new HTable(tableName, this, tableConfig, rpcCallerFactory, rpcControllerFactory,
pool);
>     }
> {code}



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

Mime
View raw message