hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrew Purtell (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (HBASE-2907) [rest/stargate] Improve error response when trying to create a scanner on a nonexistant table
Date Wed, 06 Oct 2010 22:34:33 GMT

     [ https://issues.apache.org/jira/browse/HBASE-2907?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Andrew Purtell resolved HBASE-2907.
-----------------------------------

      Resolution: Fixed
    Hadoop Flags: [Reviewed]

Committed to trunk and 0.20 branch. Thanks for the review Jon.

> [rest/stargate] Improve error response when trying to create a scanner on a nonexistant
table
> ---------------------------------------------------------------------------------------------
>
>                 Key: HBASE-2907
>                 URL: https://issues.apache.org/jira/browse/HBASE-2907
>             Project: HBase
>          Issue Type: Improvement
>          Components: rest
>            Reporter: Kieron Briggs
>            Assignee: Andrew Purtell
>            Priority: Minor
>             Fix For: 0.20.7, 0.90.0
>
>
> Since 0.20.4, an attempt to create a scanner for a nonexistant table receives a "400
Bad Request" response with no furthur information. Prior to 0.20.4 it would receive a "500
org.apache.hadoop.hbase.TableNotFoundException: <table>" response with a stack trace
in the body.
> Neither of these is ideal - the 400 fails to identify what aspect of the request was
bad, and the 500 incorrectly suggests that the error was internal. Ideally the error should
be a 400 error with information in the body identifying the nature of the problem.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message