[
https://issues.apache.org/jira/browse/HBASE-7782?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14111254#comment-14111254
]
Hudson commented on HBASE-7782:
-------------------------------
FAILURE: Integrated in HBase-TRUNK #5433 (See
[https://builds.apache.org/job/HBase-TRUNK/5433/])
HBASE-7782 HBaseTestingUtility.truncateTable() not acting like CLI (Sean
Busbey) (stack: rev aada70053b37c4ac113f12c682ca61964af36847)
*
hbase-server/src/test/java/org/apache/hadoop/hbase/replication/regionserver/TestReplicationSink.java
* hbase-server/src/test/java/org/apache/hadoop/hbase/HBaseTestingUtility.java
*
hbase-server/src/test/java/org/apache/hadoop/hbase/replication/TestReplicationChangingPeerRegionservers.java
*
hbase-server/src/test/java/org/apache/hadoop/hbase/replication/TestReplicationSmallTests.java
> HBaseTestingUtility.truncateTable() not acting like CLI
> -------------------------------------------------------
>
> Key: HBASE-7782
> URL: https://issues.apache.org/jira/browse/HBASE-7782
> Project: HBase
> Issue Type: Improvement
> Components: test
> Affects Versions: 0.94.3
> Reporter: Adrien Mogenet
> Assignee: Sean Busbey
> Priority: Minor
> Labels: cli, hbasetest, test
> Fix For: 2.0.0
>
> Attachments: HBASE-7782.patch
>
>
> I would like to discuss the behavior of the truncateTable() method of
> HBaseTestingUtility. It's currently only removing the data through a
> scan/delete pattern.
> However, the truncate command in CLI is doing additional things: it disables
> the tables, drop, creates (with similar column descriptors) and then enables
> the table.
> I think the truncateTable() method is misleading; for example I used it to
> force a coprocessor to be reloaded, but it did not. Of course I can disable
> and enable the table by myself within my unit test, but perhaps it deserves
> to be discussed?
--
This message was sent by Atlassian JIRA
(v6.2#6252)
