[
https://issues.apache.org/jira/browse/HBASE-5398?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13208383#comment-13208383
]
Hudson commented on HBASE-5398:
-------------------------------
Integrated in HBase-0.92 #285 (See
[https://builds.apache.org/job/HBase-0.92/285/])
HBASE-5398 HBase shell disable_all/enable_all/drop_all promp wrong tables
for confirmation (Revision 1244171)
Result = FAILURE
stack :
Files :
* /hbase/branches/0.92/CHANGES.txt
* /hbase/branches/0.92/src/main/ruby/shell/commands/disable_all.rb
* /hbase/branches/0.92/src/main/ruby/shell/commands/drop_all.rb
* /hbase/branches/0.92/src/main/ruby/shell/commands/enable_all.rb
> 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.1
>
> 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
