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

Hudson commented on HBASE-22157:
--------------------------------

Results for branch branch-2.2
        [build #153 on 
builds.a.o|https://builds.apache.org/job/HBase%20Nightly/job/branch-2.2/153/]: 
(/) *{color:green}+1 overall{color}*
----
details (if available):

(/) {color:green}+1 general checks{color}
-- For more information [see general 
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2.2/153//General_Nightly_Build_Report/]




(/) {color:green}+1 jdk8 hadoop2 checks{color}
-- For more information [see jdk8 (hadoop2) 
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2.2/153//JDK8_Nightly_Build_Report_(Hadoop2)/]


(/) {color:green}+1 jdk8 hadoop3 checks{color}
-- For more information [see jdk8 (hadoop3) 
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2.2/153//JDK8_Nightly_Build_Report_(Hadoop3)/]


(/) {color:green}+1 source release artifact{color}
-- See build output for details.


(/) {color:green}+1 client integration test{color}


> Include the cause when constructing RestoreSnapshotException in 
> restoreSnapshot
> -------------------------------------------------------------------------------
>
>                 Key: HBASE-22157
>                 URL: https://issues.apache.org/jira/browse/HBASE-22157
>             Project: HBase
>          Issue Type: Sub-task
>          Components: Admin
>            Reporter: Duo Zhang
>            Assignee: Duo Zhang
>            Priority: Major
>             Fix For: 3.0.0, 2.2.0, 2.3.0
>
>         Attachments: HBASE-22157.patch
>
>
> When implementing HBASE-21718, a snapshot related UT fails because of the 
> incorrect cause of RestoreSnapshotException. Finally I found that we just a 
> create a RestoreSnapshotException without providing the cause in 
> restoreSnapshot.
> We should fix this.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to