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

Hudson commented on HBASE-22961:
--------------------------------

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

(x) {color:red}-1 general checks{color}
-- For more information [see general 
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2/2226//General_Nightly_Build_Report/]




(x) {color:red}-1 jdk8 hadoop2 checks{color}
-- For more information [see jdk8 (hadoop2) 
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2/2226//JDK8_Nightly_Build_Report_(Hadoop2)/]


(x) {color:red}-1 jdk8 hadoop3 checks{color}
-- For more information [see jdk8 (hadoop3) 
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2/2226//JDK8_Nightly_Build_Report_(Hadoop3)/]


(/) {color:green}+1 source release artifact{color}
-- See build output for details.


(/) {color:green}+1 client integration test{color}


> Deprecate hbck1 in core
> -----------------------
>
>                 Key: HBASE-22961
>                 URL: https://issues.apache.org/jira/browse/HBASE-22961
>             Project: HBase
>          Issue Type: Bug
>          Components: hbck
>            Reporter: stack
>            Assignee: stack
>            Priority: Major
>             Fix For: 3.0.0, 2.3.0, 2.2.1, 2.1.7
>
>         Attachments: 0001-HBASE-22961-Deprecate-hbck1-in-core.patch, 
> 0001-HBASE-22961-Deprecate-hbck1-in-core.patch, HBASE-22961.master.001.patch, 
> HBASE-22961.master.002.patch
>
>
> HBaseFsck is just noted as read-only (along w/ noting that it is unreliable 
> and shouldn't be used). Need to add deprecation so can be removed especially 
> now that hbck2 has been built up and that the bulk of hbck1 is not 
> rejiggered, repurposed to serve hbck2 and living out in hbase-operator-tools.



--
This message was sent by Atlassian Jira
(v8.3.2#803003)

Reply via email to