Mailing-List: contact dev-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@hbase.apache.org
Date: Tue, 7 Jun 2016 19:30:21 +0000 (UTC)
From: "Bryan Beaudreault (JIRA)" <jira@apache.org>
To: dev@hbase.apache.org
Message-ID: <JIRA.12976588.1465327814000.18509.1465327821349@Atlassian.JIRA>
In-Reply-To: <JIRA.12976588.1465327814000@Atlassian.JIRA>
References: <JIRA.12976588.1465327814000@Atlassian.JIRA> <JIRA.12976588.1465327814358@arcas>
Subject: [jira] [Created] (HBASE-15981) Stripe and Date-tiered compactions
 inaccurately suggest disabling table in docs
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Tue, 07 Jun 2016 19:30:24 -0000

Bryan Beaudreault created HBASE-15981:
-----------------------------------------

             Summary: Stripe and Date-tiered compactions inaccurately suggest disabling table in docs
                 Key: HBASE-15981
                 URL: https://issues.apache.org/jira/browse/HBASE-15981
             Project: HBase
          Issue Type: Improvement
          Components: documentation
            Reporter: Bryan Beaudreault
            Priority: Minor


{{hbase.online.schema.update.enable}} is set to true in later versions of HBase. However, the documentation in the book around configuration Stripe and Date-tiered compactions instruct the user to disable a table before changing configuration. According to Enis on the user list, this is not necessary:

{quote}
Disabling the table should not be needed. From the stripe compaction
perspective, deploying this in a disabled table versus in an online alter
table is not different at all. The "hbase.online.schema.update.enable"
property was fixing some possible race conditions that were fixed long time
ago.
{quote}

We should update the book to remove this inaccurate messaging.


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