You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@hbase.apache.org by "Adrien Mogenet (JIRA)" <ji...@apache.org> on 2013/02/06 21:29:13 UTC

[jira] [Created] (HBASE-7782) HBaseTestingUtility.truncateTable() not acting like CLI

Adrien Mogenet created HBASE-7782:
-------------------------------------

             Summary: 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
            Priority: Minor


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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira