hbase-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "stack (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (HBASE-10602) Cleanup HTable public interface
Date Wed, 26 Nov 2014 19:24:13 GMT

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

stack resolved HBASE-10602.
    Resolution: Fixed

Resolving. All subtasks done.  The cleanup asked for has been done (we got something better
than what was asked for!).  Reopen if I have it wrong.

> Cleanup HTable public interface
> -------------------------------
>                 Key: HBASE-10602
>                 URL: https://issues.apache.org/jira/browse/HBASE-10602
>             Project: HBase
>          Issue Type: Umbrella
>          Components: Client, Usability
>            Reporter: Nick Dimiduk
>            Assignee: Enis Soztutar
>            Priority: Blocker
>             Fix For: 0.99.2
>         Attachments: hbase-10602_v1.patch
> HBASE-6580 replaced the preferred means of HTableInterface acquisition to the HConnection#getTable
factory methods. HBASE-9117 removes the HConnection cache, placing the burden of responsible
connection cleanup on whomever acquires it.
> The remaining HTable constructors use a Connection instance and manage their own HConnection
on the callers behalf. This is convenient but also a surprising source of poor performance
for anyone accustomed to the previous connection caching behavior. I propose deprecating those
remaining constructors for 0.98/0.96 and removing them for 1.0.
> While I'm at it, I suggest we pursue some API hygiene in general and convert HTable into
an interface. I'm sure there are method overloads for accepting String/byte[]/TableName where
just TableName is sufficient. Can that be done for 1.0 as well?

This message was sent by Atlassian JIRA

View raw message