hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vandana Ayyalasomayajula (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HBASE-9524) Multi row get does not return any results even if any one of the rows specified in the query is missing and improve exception handling
Date Fri, 13 Sep 2013 22:46:52 GMT

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

Vandana Ayyalasomayajula updated HBASE-9524:
--------------------------------------------

    Attachment: hbase-9524_trunk.00.patch

Initial patch for trunk. I have refactored TestRowResource into two test files, TestDeleteRow
and TestGetAndPutResource as the test was running more than 30 secs ( which is the desired
limit for medium tests).
                
> Multi row get does not return any results even if any one of the rows specified in the
query is missing and improve exception handling
> --------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: HBASE-9524
>                 URL: https://issues.apache.org/jira/browse/HBASE-9524
>             Project: HBase
>          Issue Type: Improvement
>          Components: REST
>            Reporter: Vandana Ayyalasomayajula
>            Assignee: Vandana Ayyalasomayajula
>            Priority: Minor
>         Attachments: hbase-9524_trunk.00.patch
>
>
> When a client tries to retrieve multiple rows using REST API, even if one of the specified
rows does not exist, 404 is returned. The correct way should be to return the result for the
found rows and ignore the non-existent ones. Also, in the current code base, only some exceptions
are handled, if some exception like Access denied or no column found exception is throws by
the APIs, 500 ( server not found) is returned to user. This is leaves the end user wondering
what caused the rest command to fail. 

--
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

Mime
View raw message