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 2AC4110C97 for ; Wed, 2 Sep 2015 11:26:46 +0000 (UTC) Received: (qmail 51371 invoked by uid 500); 2 Sep 2015 11:26:46 -0000 Delivered-To: apmail-hbase-issues-archive@hbase.apache.org Received: (qmail 51324 invoked by uid 500); 2 Sep 2015 11:26:46 -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 51313 invoked by uid 99); 2 Sep 2015 11:26:45 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 02 Sep 2015 11:26:45 +0000 Date: Wed, 2 Sep 2015 11:26:45 +0000 (UTC) From: "Nick.han (JIRA)" To: issues@hbase.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (HBASE-14332) Show the table state when we encounter exception while disabling / enabling table MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/HBASE-14332?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14727190#comment-14727190 ] Nick.han commented on HBASE-14332: ---------------------------------- It's my pleasure. > Show the table state when we encounter exception while disabling / enabling table > --------------------------------------------------------------------------------- > > Key: HBASE-14332 > URL: https://issues.apache.org/jira/browse/HBASE-14332 > Project: HBase > Issue Type: Improvement > Affects Versions: 2.0.0 > Reporter: Nick.han > Assignee: Nick.han > Priority: Minor > Fix For: 2.0.0 > > Attachments: HBASE-14332.patch, HBASE-14332_v2.patch, HBASE-14332_v3.patch, HBASE-14332_v3.patch > > > This patch is a advice for good user experience > reason: > When we disable a table and the table is not enabled,we receive a exception,but the exception is too brief,some time we want to know what state is the table in,so that we can know why the table can't be disable.For example,I once encountered a problem the table is neither disable nor enable when my region server crash down,if we give the table state,I will find the problem more quickly . -- This message was sent by Atlassian JIRA (v6.3.4#6332)