hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Srikanth Srungarapu (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-7782) HBaseTestingUtility.truncateTable() not acting like CLI
Date Sat, 23 May 2015 01:06:17 GMT

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

Srikanth Srungarapu commented on HBASE-7782:
--------------------------------------------

Any particular reason why this fix is not backported to 1.0+ and 0.98 branches?

> 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)

Mime
View raw message