[
https://issues.apache.org/jira/browse/HBASE-13789?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14565688#comment-14565688
]
Hudson commented on HBASE-13789:
--------------------------------
SUCCESS: Integrated in HBase-0.98 #1010 (See
[https://builds.apache.org/job/HBase-0.98/1010/])
HBASE-13789 ForeignException should not be sent to the client (matteo.bertozzi:
rev a648e532c7fa6519de80861a24305dc89dd0d78d)
* hbase-server/src/main/java/org/apache/hadoop/hbase/master/HMaster.java
> ForeignException should not be sent to the client
> -------------------------------------------------
>
> Key: HBASE-13789
> URL: https://issues.apache.org/jira/browse/HBASE-13789
> Project: HBase
> Issue Type: Bug
> Components: Client, master
> Affects Versions: 2.0.0, 0.98.13, 1.0.1.1, 1.1.0.1
> Reporter: Matteo Bertozzi
> Assignee: Matteo Bertozzi
> Priority: Minor
> Attachments: HBASE-13789-v0.patch
>
>
> ForeignException is in hbase-server so the client will not be able to
> deserialize it, and also it will hide the DoNotRetryException of the cause.
> I haven't found an easy way to test it, aside manually looking at the logs.
> and this stuff will go away with proc-v2. so for now the easy workaround is
> catch the ForeignException in the master which are just the few places
> related to proc-v1 and throw the cause to the client
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
