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

Posted to issues@hbase.apache.org by "Jean-Daniel Cryans (JIRA)" <ji...@apache.org> on 2011/02/23 00:04:38 UTC

[jira] Created: (HBASE-3557) Quick disable call to drop a table

Quick disable call to drop a table
----------------------------------

                 Key: HBASE-3557
                 URL: https://issues.apache.org/jira/browse/HBASE-3557
             Project: HBase
          Issue Type: New Feature
            Reporter: Jean-Daniel Cryans
             Fix For: 0.92.0


>From the mailing list, it seems that a feature that enables the disabling of tables without having to wait for regions to flush would be quite popular. In the case where you do rapid development, you often churn through tables and need to drop/truncate them often. This is often true after a big MR job when the data isn't right.

As a solution, I'm thinking of a flag that you can pass to the disable command to jettison the memstores like we already have when doing an emergency shutdown.

-- 
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] Commented: (HBASE-3557) Quick disable call to drop a table

Posted by "Lars George (JIRA)" <ji...@apache.org>.

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

Lars George commented on HBASE-3557:
------------------------------------

+1, this only ever happened to me with bulk imports and then being able to quickly drop the incorrect table for a restart.

> Quick disable call to drop a table
> ----------------------------------
>
>                 Key: HBASE-3557
>                 URL: https://issues.apache.org/jira/browse/HBASE-3557
>             Project: HBase
>          Issue Type: New Feature
>            Reporter: Jean-Daniel Cryans
>             Fix For: 0.92.0
>
>
> From the mailing list, it seems that a feature that enables the disabling of tables without having to wait for regions to flush would be quite popular. In the case where you do rapid development, you often churn through tables and need to drop/truncate them often. This is often true after a big MR job when the data isn't right.
> As a solution, I'm thinking of a flag that you can pass to the disable command to jettison the memstores like we already have when doing an emergency shutdown.

-- 
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira