Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Fri, 19 Sep 2014 20:44:34 +0000 (UTC)
From: "stack (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: <JIRA.12701621.1394836191000.81269.1411159474201@Atlassian.JIRA>
In-Reply-To: <JIRA.12701621.1394836191000@Atlassian.JIRA>
References: <JIRA.12701621.1394836191000@Atlassian.JIRA>
 <JIRA.12701621.1394836191977@arcas>
Subject: [jira] [Updated] (HBASE-10757) Change HTable class doc so it sends
 people to HCM getting instances
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

stack updated HBASE-10757:
--------------------------
      Resolution: Fixed
    Hadoop Flags: Reviewed
          Status: Resolved  (was: Patch Available)

Thanks for +1 [~enis] Applied to master and branch-1.

On deprecating HTable and HBaseAdmin, if the constructors are shutdown, in essence they are effectively unavailable.  Deprecating them might be too radical a step.  On other hand, the landscape here is shifting fast and a nice clean API is starting to pop out..... How about asking the question again around 0.99.3?  The answer may be more plain then?

> Change HTable class doc so it sends people to HCM getting instances
> -------------------------------------------------------------------
>
>                 Key: HBASE-10757
>                 URL: https://issues.apache.org/jira/browse/HBASE-10757
>             Project: HBase
>          Issue Type: Bug
>            Reporter: stack
>            Assignee: stack
>            Priority: Critical
>             Fix For: 2.0.0, 0.99.1
>
>         Attachments: 10757.txt
>
>
> The HTable class doc does not reflect the new regime where you are meant to go via cluster connection to get an instance.
> Getting an HTable otherwise also makes for some strange issues:  See "Occasional GSSException that brings down region server" on mailing list.


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