[
https://issues.apache.org/jira/browse/HBASE-28656?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17856925#comment-17856925
]
Hudson commented on HBASE-28656:
--------------------------------
Results for branch branch-3
[build #233 on
builds.a.o|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-3/233/]:
(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/branch-3/233/General_20Nightly_20Build_20Report/]
(x) {color:red}-1 jdk8 hadoop3 checks{color}
-- Something went wrong running this stage, please [check relevant console
output|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-3/233//console].
(x) {color:red}-1 jdk11 hadoop3 checks{color}
-- For more information [see jdk11
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-3/233/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}
> Optimize the verifyCopyResult logic in ExportSnapshot
> -----------------------------------------------------
>
> Key: HBASE-28656
> URL: https://issues.apache.org/jira/browse/HBASE-28656
> Project: HBase
> Issue Type: Improvement
> Reporter: Liangjun He
> Assignee: Liangjun He
> Priority: Critical
> Labels: pull-request-available
> Fix For: 3.0.0-beta-2
>
>
> In [HBASE-28625|https://issues.apache.org/jira/browse/HBASE-28625], we added
> checksum logic comparison for ExportSnapshot files, but the checksum
> verification scenarios were too simple. This issue aims to address the
> existing problem. For detailed discussion, please refer to PR
> [5950|https://github.com/apache/hbase/pull/5950].
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
