[
https://issues.apache.org/jira/browse/HBASE-26720?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17508071#comment-17508071
]
Hudson commented on HBASE-26720:
--------------------------------
Results for branch master
[build #538 on
builds.a.o|https://ci-hbase.apache.org/job/HBase%20Nightly/job/master/538/]:
(x) *{color:red}-1 overall{color}*
----
details (if available):
(/) {color:green}+1 general checks{color}
-- For more information [see general
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/master/538/General_20Nightly_20Build_20Report/]
(x) {color:red}-1 jdk8 hadoop3 checks{color}
-- For more information [see jdk8 (hadoop3)
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/master/538/JDK8_20Nightly_20Build_20Report_20_28Hadoop3_29/]
(x) {color:red}-1 jdk11 hadoop3 checks{color}
-- For more information [see jdk11
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/master/538/JDK11_20Nightly_20Build_20Report_20_28Hadoop3_29/]
(/) {color:green}+1 source release artifact{color}
-- See build output for details.
(/) {color:green}+1 client integration test{color}
> ExportSnapshot should validate the source snapshot before copying files
> -----------------------------------------------------------------------
>
> Key: HBASE-26720
> URL: https://issues.apache.org/jira/browse/HBASE-26720
> Project: HBase
> Issue Type: Improvement
> Components: snapshots
> Affects Versions: 0.99.0, 1.0.0, 3.0.0-alpha-1, 2.0.0
> Reporter: David Manning
> Assignee: xichaomin
> Priority: Major
> Fix For: 2.5.0, 2.6.0, 3.0.0-alpha-3, 2.4.12
>
> Attachments: HBASE-26720.v01.patch
>
>
> Running {{ExportSnapshot}} with default parameters will copy the snapshot to
> a target location, and then use {{verifySnapshot}} to validate the integrity
> of the written snapshot. However, it is possible for the source snapshot to
> be invalid which leads to an invalid exported snapshot.
> We can validate the source snapshot before export.
> By default, we can validate the source snapshot unless the
> {{-no-target-verify}} parameter is set. We could also introduce a separate
> parameter for {{-no-source-verify}} if an operator wanted to validate the
> target but not validate the source for some reason, to provide some amount of
> backwards compatibility if that scenario is important.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
