[
https://issues.apache.org/jira/browse/HBASE-9524?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13766761#comment-13766761
]
Nick Dimiduk commented on HBASE-9524:
-------------------------------------
bq. The correct way should be to return the result for the found rows and
ignore the non-existent ones.
That sounds good to me; it's consistent with the shell in so much as requesting
a row which doesn't exist returns empty results rather than throwing. What
happens if none of the rows are found? Should an empty result set be returned
or would that case return 404 -- maintaining consistency with the rest of REST?
bq. only some exceptions are handled
Ah, right. I'm looking forward to seeing what you come up with.
> 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
>
> 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
