You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "stack (Commented) (JIRA)" <ji...@apache.org> on 2012/02/14 19:52:01 UTC
[jira] [Commented] (HBASE-5398) HBase shell
disable_all/enable_all/drop_all promp wrong tables for confirmation
[ https://issues.apache.org/jira/browse/HBASE-5398?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13207899#comment-13207899 ]
stack commented on HBASE-5398:
------------------------------
Patch looks good. How is disable_all supposed to work? Its supposed to take a regex pattern?
> HBase shell disable_all/enable_all/drop_all promp wrong tables for confirmation
> -------------------------------------------------------------------------------
>
> Key: HBASE-5398
> URL: https://issues.apache.org/jira/browse/HBASE-5398
> Project: HBase
> Issue Type: Bug
> Components: scripts
> Affects Versions: 0.94.0, 0.92.0
> Reporter: Jimmy Xiang
> Assignee: Jimmy Xiang
> Fix For: 0.94.0, 0.92.0
>
> Attachments: hbase-5398.patch
>
>
> When using hbase shell to disable_all/enable_all/drop_all tables, the tables prompted for confirmation are wrong.
> For example, disable_all 'test*'
> will ask form confirmation to diable tables like:
> mytest1
> test123
> Fortunately, these tables will not be disabled actually since Java pattern doesn't match this way.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira