hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-15981) Stripe and Date-tiered compactions inaccurately suggest disabling table in docs
Date Tue, 07 Jun 2016 23:13:21 GMT

    [ https://issues.apache.org/jira/browse/HBASE-15981?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15319656#comment-15319656

Hudson commented on HBASE-15981:

FAILURE: Integrated in HBase-Trunk_matrix #1007 (See [https://builds.apache.org/job/HBase-Trunk_matrix/1007/])
HBASE-15981 Remove references to disabling table in docs around stripe (stack: rev 2da090f9a3ca42b07f342035c952ce0465c67265)
* src/main/asciidoc/_chapters/architecture.adoc

> 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
>            Assignee: Bryan Beaudreault
>            Priority: Minor
>             Fix For: 2.0.0
>         Attachments: HBASE-15981.patch
> {{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

View raw message