Return-Path: X-Original-To: apmail-hbase-issues-archive@www.apache.org Delivered-To: apmail-hbase-issues-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id E5D12102F5 for ; Sat, 27 Jul 2013 00:39:50 +0000 (UTC) Received: (qmail 722 invoked by uid 500); 27 Jul 2013 00:39:48 -0000 Delivered-To: apmail-hbase-issues-archive@hbase.apache.org Received: (qmail 657 invoked by uid 500); 27 Jul 2013 00:39:48 -0000 Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Delivered-To: mailing list issues@hbase.apache.org Received: (qmail 515 invoked by uid 99); 27 Jul 2013 00:39:48 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 27 Jul 2013 00:39:48 +0000 Date: Sat, 27 Jul 2013 00:39:48 +0000 (UTC) From: "Bene Guo (JIRA)" To: issues@hbase.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Created] (HBASE-9054) HBaseAdmin#isTableDisabled() should check table existence before checking zk state. MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 Bene Guo created HBASE-9054: ------------------------------- Summary: HBaseAdmin#isTableDisabled() should check table existence before checking zk state. Key: HBASE-9054 URL: https://issues.apache.org/jira/browse/HBASE-9054 Project: HBase Issue Type: Bug Components: Admin Affects Versions: 0.94.10 Reporter: Bene Guo Fix For: 0.94.11 To avoid compatibility issues with older versions HBaseAdmin#isTableDisabled and HBaseAdmin#isTableEnabled()(The HBASE-8538 fix isTableEnabled.) returning true even if the table state is null. Its also returning true even a table is not present. We should confirm table existence from .META. before checking in zk. If table not present or deleted, then It will throw TableNotFoundException. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira