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

Hudson commented on HBASE-26700:
--------------------------------

Results for branch master
        [build #502 on 
builds.a.o|https://ci-hadoop.apache.org/job/HBase/job/HBase%20Nightly/job/master/502/]:
 (x) *{color:red}-1 overall{color}*
----
details (if available):

(/) {color:green}+1 general checks{color}
-- For more information [see general 
report|https://ci-hadoop.apache.org/job/HBase/job/HBase%20Nightly/job/master/502/General_20Nightly_20Build_20Report/]






(x) {color:red}-1 jdk8 hadoop3 checks{color}
-- For more information [see jdk8 (hadoop3) 
report|https://ci-hadoop.apache.org/job/HBase/job/HBase%20Nightly/job/master/502/JDK8_20Nightly_20Build_20Report_20_28Hadoop3_29/]


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


> The way we bypass broken track file is not enough in StoreFileListFile
> ----------------------------------------------------------------------
>
>                 Key: HBASE-26700
>                 URL: https://issues.apache.org/jira/browse/HBASE-26700
>             Project: HBase
>          Issue Type: Sub-task
>          Components: HFile
>            Reporter: Duo Zhang
>            Assignee: Duo Zhang
>            Priority: Critical
>             Fix For: 2.6.0, 3.0.0-alpha-3
>
>
> When implementing HBASE-26690, I found that a pb message can be parsed with 
> partial bytes, if we stop at some special point.
> So we can not rely on the pb parser to always throw 
> InvalidProtocolBufferException for us, we need to detect the incomplete file 
> by ourselves.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

Reply via email to