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 0A14617B3F for ; Thu, 19 Mar 2015 00:08:39 +0000 (UTC) Received: (qmail 63608 invoked by uid 500); 19 Mar 2015 00:08:38 -0000 Delivered-To: apmail-hbase-issues-archive@hbase.apache.org Received: (qmail 63554 invoked by uid 500); 19 Mar 2015 00:08:38 -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 63541 invoked by uid 99); 19 Mar 2015 00:08:38 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 19 Mar 2015 00:08:38 +0000 Date: Thu, 19 Mar 2015 00:08:38 +0000 (UTC) From: "Andrew Purtell (JIRA)" To: issues@hbase.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Issue Comment Deleted] (HBASE-12967) Invalid FQCNs in alter table command leaves the table unusable 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-12967?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Purtell updated HBASE-12967: ----------------------------------- Comment: was deleted (was: Moved out to 0.98.12) > Invalid FQCNs in alter table command leaves the table unusable > -------------------------------------------------------------- > > Key: HBASE-12967 > URL: https://issues.apache.org/jira/browse/HBASE-12967 > Project: HBase > Issue Type: Bug > Reporter: ramkrishna.s.vasudevan > Priority: Critical > Fix For: 2.0.0, 1.0.1, 1.1.0, 0.98.13 > > > Refer to this thread > http://osdir.com/ml/general/2015-02/msg03547.html > A user tries to alter a table with a new split policy. Due to an invalid classname the table does not get enabled and the table becomes unusable. I think Procedure V2 is a long term soln for this but I think we atleast need to provide a work around or a set of steps to come out of this. Any fix before Procedure V2 comes into place would useful for the already released versions. -- This message was sent by Atlassian JIRA (v6.3.4#6332)