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

Hudson commented on HBASE-28457:
--------------------------------

Results for branch master
        [build #1046 on 
builds.a.o|https://ci-hbase.apache.org/job/HBase%20Nightly/job/master/1046/]: 
(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/1046/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/1046/JDK8_20Nightly_20Build_20Report_20_28Hadoop3_29/]


(/) {color:green}+1 jdk11 hadoop3 checks{color}
-- For more information [see jdk11 
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/master/1046/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}


> Introduce a version field in file based tracker record
> ------------------------------------------------------
>
>                 Key: HBASE-28457
>                 URL: https://issues.apache.org/jira/browse/HBASE-28457
>             Project: HBase
>          Issue Type: Sub-task
>          Components: HFile
>            Reporter: Duo Zhang
>            Assignee: Duo Zhang
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 2.6.0, 3.0.0-beta-2, 2.5.9
>
>
> Per the discussion around HBASE-27826 and the related design doc, we all 
> agree that we should add version field to store file tracker, so when 
> downgrading, we will know that we will miss something when reading a tracker 
> file with higher version and fail the initialization, instead of ignore it 
> silently and may cause data loss.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to