[ 
https://issues.apache.org/jira/browse/HBASE-9524?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13778271#comment-13778271
 ] 

Hadoop QA commented on HBASE-9524:
----------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  
http://issues.apache.org/jira/secure/attachment/12603137/hbase-9524_trunk.00.patch
  against trunk revision .

    {color:green}+1 @author{color}.  The patch does not contain any @author 
tags.

    {color:green}+1 tests included{color}.  The patch appears to include 14 new 
or modified tests.

    {color:red}-1 patch{color}.  The patch command could not apply the patch.

Console output: 
https://builds.apache.org/job/PreCommit-HBASE-Build/7381//console

This message is automatically generated.
                
> 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

Reply via email to