[
https://issues.apache.org/jira/browse/HBASE-7782?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sean Busbey resolved HBASE-7782.
--------------------------------
Resolution: Fixed
Hadoop Flags: Incompatible change,Reviewed (was: Reviewed)
Release Note:
HBaseTestingUtility now uses the truncate API added in HBASE-8332 so that calls
to HBTU.truncateTable will behave like the shell command: effectively dropping
the table and recreating a new one with the same split points.
Previously, HBTU.truncateTable instead issued deletes for all the data already
in the table. If you wish to maintain the same behavior, you should use the
newly added HBTU.deleteTableData method.
> 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.3.4#6332)
