[
https://issues.apache.org/jira/browse/HBASE-15209?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15135716#comment-15135716
]
Hudson commented on HBASE-15209:
--------------------------------
FAILURE: Integrated in HBase-1.2 #533 (See
[https://builds.apache.org/job/HBase-1.2/533/])
HBASE-15209 (compatibility) Disable table in (stack: rev
c746f1250d90b4386ec3d4db035fa741e845d093)
* hbase-server/src/test/java/org/apache/hadoop/hbase/HBaseTestingUtility.java
> disable table in HBaseTestingUtility.truncateTable
> ---------------------------------------------------
>
> Key: HBASE-15209
> URL: https://issues.apache.org/jira/browse/HBASE-15209
> Project: HBase
> Issue Type: Bug
> Reporter: Appy
> Assignee: Appy
> Priority: Minor
> Labels: compatibility
> Fix For: 2.0.0, 1.2.0, 1.3.0
>
> Attachments: HBASE-15209-branch-1-v1.patch,
> HBASE-15209-branch-1-v2.patch, HBASE-15209-v1.patch, HBASE-15209-v2.patch
>
>
> Old truncate table expected table to be enabled and removed rows by scanning
> over them.
> In HBASE-13764, the function was changed to make it consistent with how shell
> worked, so new one used admin.truncateTable.
> Since HBTU.truncateTable expects table to be enabled (backward compat)
> whereas admin.truncateTable expects table to be disabled, we should add a
> disable table there.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
