You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Elliott Clark (JIRA)" <ji...@apache.org> on 2012/10/02 02:40:07 UTC
[jira] [Commented] (HBASE-6914) Scans/Gets/Mutations don't give a
good error if the table is disabled.
[ https://issues.apache.org/jira/browse/HBASE-6914?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13467365#comment-13467365 ]
Elliott Clark commented on HBASE-6914:
--------------------------------------
Pretty simple patch that results in:
{code}
hbase(main):001:0> disable 't1'
2012-10-01 17:37:45.631 java[84004:1203] Unable to load realm info from SCDynamicStore
0 row(s) in 8.3820 seconds
hbase(main):002:0> scan 't1'
ERROR: org.apache.hadoop.hbase.DoNotRetryIOException: t1 is disabled.
Here is some help for this command:
Scan a table; pass table name and optionally a dictionary of scanner
specifications. Scanner specifications may include one or more of:
TIMERANGE, FILTER, LIMIT, STARTROW, STOPROW, TIMESTAMP, MAXLENGTH,
or COLUMNS, CACHE
If no columns are specified, all columns will be scanned.
To scan all members of a column family, leave the qualifier empty as in
'col_family:'.
{code}
> Scans/Gets/Mutations don't give a good error if the table is disabled.
> ----------------------------------------------------------------------
>
> Key: HBASE-6914
> URL: https://issues.apache.org/jira/browse/HBASE-6914
> Project: HBase
> Issue Type: Improvement
> Reporter: Elliott Clark
> Assignee: Elliott Clark
> Fix For: 0.94.3, 0.96.0
>
> Attachments: HBASE-6914-0.patch
>
>
> Scan a table that is disabled will have the client retry multiple times and then will error out with NotServingRegionException. If the table is disabled there's no need to re-try and the message should be more explicit.
--
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