[
https://issues.apache.org/jira/browse/HBASE-7155?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13502420#comment-13502420
]
stack commented on HBASE-7155:
------------------------------
[~dferro] How hard to do your option #2 above. Rather than remove all IEs.,
given the client isa blocking client, ideally it should be interruptible if it
is stuck. That'd mean that IE could come up and out of our APIs?
Agree fix doc. at least. Thanks for digging in here Daniel.
> Excessive usage of InterruptedException where it can't be thrown
> ----------------------------------------------------------------
>
> Key: HBASE-7155
> URL: https://issues.apache.org/jira/browse/HBASE-7155
> Project: HBase
> Issue Type: Bug
> Reporter: Daniel Gómez Ferro
> Assignee: Daniel Gómez Ferro
> Attachments: HBASE-7155.patch
>
>
> RootRegionTracker.getRootRegionLocation() declares that it can throw an
> InterruptedException, but it can't. This exception is rethrown by many other
> functions reaching the HBaseAdmin API.
> If we remove the throws statement from the HBaseAdmin API libraries already
> compiled will work fine, but if the user is trying to catch an
> InterruptedException around one of those methods the compiler will complain.
> Should we clean this up?
--
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
