[
https://issues.apache.org/jira/browse/HBASE-6668?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13454378#comment-13454378
]
stack commented on HBASE-6668:
------------------------------
I don't think the current behavior that bad.... could be more pleasant but I'd
suggest that there are better places to dig where the yields could be much
larger if you would like to improve 'user experience'.
> disable in shell may make confused to user
> -------------------------------------------
>
> Key: HBASE-6668
> URL: https://issues.apache.org/jira/browse/HBASE-6668
> Project: HBase
> Issue Type: Bug
> Components: shell
> Affects Versions: 0.94.1
> Reporter: Zhou wenjian
> Assignee: Zhou wenjian
>
> hbase(main):002:0> disable 'logTable'
> 0 row(s) in 2.0910 seconds
> hbase(main):003:0> disable 'logTable'
> 0 row(s) in 0.0260 seconds
> and we can found table are disabled in log when disable first appears
> but when i disable it again the client just return seemed to be sucessful and
> I can not find any log described it in the log.
> look into the admin.rb, find below
>
> #----------------------------------------------------------------------------------------------
> # Disables a table
> def disable(table_name)
> tableExists(table_name)
> return if disabled?(table_name)
> @admin.disableTable(table_name)
> end
> that would confuse us when we found it disabled already but returns nothing
--
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
