[
https://issues.apache.org/jira/browse/HBASE-3670?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13024942#comment-13024942
]
Harsh J Chouraria commented on HBASE-3670:
------------------------------------------
Ok, I believe if we mention an exception is thrown it is alright (its always
better the dev knows the causes of a failure). Perhaps we can add it as an
@throws along with IOExceptions, but am not sure if that's considered as API
breakage.
I'm now confused on what class of docs to change here, the HTableInterface or
the HTable itself? Both have duplicate logs at places, and different in some.
> Fix error handling in get(List<Get> gets)
> -----------------------------------------
>
> Key: HBASE-3670
> URL: https://issues.apache.org/jira/browse/HBASE-3670
> Project: HBase
> Issue Type: Bug
> Components: client
> Affects Versions: 0.92.0
> Reporter: Lars George
> Fix For: 0.92.0
>
>
> See HBASE-3634 for details. The get(List<Get> gets) call needs to catch (or
> rather use a try/finally) the exception thrown by batch() and copy the Result
> instances over and return it. If that is not intended then we need to fix the
> JavaDoc in HTableInterface to reflect the new behavior.
> In general it seems to make sense to check the various methods (list based
> put, get, delete compared to batch) and agree on the correct behavior.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira