You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Hadoop QA (JIRA)" <ji...@apache.org> on 2016/08/25 01:49:20 UTC
[jira] [Commented] (HBASE-16366) Restore operation into new table
can fail
[ https://issues.apache.org/jira/browse/HBASE-16366?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15436110#comment-15436110 ]
Hadoop QA commented on HBASE-16366:
-----------------------------------
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 0m 0s {color} | {color:blue} Docker mode activated. {color} |
| {color:red}-1{color} | {color:red} patch {color} | {color:red} 0m 5s {color} | {color:red} HBASE-16366 does not apply to master. Rebase required? Wrong Branch? See https://yetus.apache.org/documentation/0.3.0/precommit-patchnames for help. {color} |
\\
\\
|| Subsystem || Report/Notes ||
| JIRA Patch URL | https://issues.apache.org/jira/secure/attachment/12825387/HBASE-16366-v1.patch |
| JIRA Issue | HBASE-16366 |
| Console output | https://builds.apache.org/job/PreCommit-HBASE-Build/3256/console |
| Powered by | Apache Yetus 0.3.0 http://yetus.apache.org |
This message was automatically generated.
> Restore operation into new table can fail
> -----------------------------------------
>
> Key: HBASE-16366
> URL: https://issues.apache.org/jira/browse/HBASE-16366
> Project: HBase
> Issue Type: Bug
> Reporter: Vladimir Rodionov
> Assignee: Vladimir Rodionov
> Attachments: HBASE-16366-v1.patch
>
>
> If restore from backup into new table we need to make sure that new table is available online.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)