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

Hadoop QA commented on HBASE-15734:
-----------------------------------

| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} patch {color} | {color:blue} 0m 1s 
{color} | {color:blue} The patch file was not named according to hbase's naming 
conventions. Please see 
https://yetus.apache.org/documentation/0.2.1/precommit-patchnames for 
instructions. {color} |
| {color:red}-1{color} | {color:red} patch {color} | {color:red} 0m 3s {color} 
| {color:red} HBASE-15734 does not apply to master. Rebase required? Wrong 
Branch? See https://yetus.apache.org/documentation/0.2.1/precommit-patchnames 
for help. {color} |
\\
\\
|| Subsystem || Report/Notes ||
| JIRA Patch URL | 
https://issues.apache.org/jira/secure/attachment/12801477/15734.v2.txt |
| JIRA Issue | HBASE-15734 |
| Console output | 
https://builds.apache.org/job/PreCommit-HBASE-Build/1683/console |
| Powered by | Apache Yetus 0.2.1   http://yetus.apache.org |


This message was automatically generated.



> Propagate exception in table backup procedures
> ----------------------------------------------
>
>                 Key: HBASE-15734
>                 URL: https://issues.apache.org/jira/browse/HBASE-15734
>             Project: HBase
>          Issue Type: Bug
>            Reporter: Ted Yu
>            Assignee: Ted Yu
>              Labels: backup
>         Attachments: 15734.v1.txt, 15734.v2.txt
>
>
> Currently we have the following in XXTableBackupProcedure:
> {code}
>           } catch (Exception e) {
>             // fail the overall backup and return
>             failBackup(env, backupInfo, backupManager, e, "Unexpected 
> BackupException : ",
>               BackupType.FULL, conf);
>             return Flow.NO_MORE_STATE;
> {code}
> However, failBackup() doesn't propagate the exception to procedure V2.
> This issue is to add setFailure() calls for the propagation.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to