[
https://issues.apache.org/jira/browse/HBASE-7415?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13617458#comment-13617458
]
Hadoop QA commented on HBASE-7415:
----------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12576088/HBASE-7415-0.94.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 3 new
or modified tests.
{color:red}-1 patch{color}. The patch command could not apply the patch.
Console output:
https://builds.apache.org/job/PreCommit-HBASE-Build/5045//console
This message is automatically generated.
> [snapshots] Add task information to snapshot operation
> ------------------------------------------------------
>
> Key: HBASE-7415
> URL: https://issues.apache.org/jira/browse/HBASE-7415
> Project: HBase
> Issue Type: New Feature
> Components: Client, master, regionserver, snapshots, Zookeeper
> Reporter: Jesse Yates
> Assignee: Jesse Yates
> Fix For: 0.95.0
>
> Attachments: HBASE-7415-0.94.patch, hbase-7415-v0.patch,
> hbase-7415-v1.patch, HBASE-7415-v1-rebase.patch, HBASE-7415-v2.patch,
> HBASE-7415-v3.patch, HBase_Snapshot_Task_UI.png
>
>
> Snapshot operations should have some sort of progresss information available
> via the WebUI so admins can track progress of operations. This should go a
> long way to enable 'good' admins to not hose their clusters by running
> concurrent snapshot operations (e.g. rename while a clone is in progress).
--
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
