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

Wellington Chevreuil commented on HBASE-24793:
----------------------------------------------

Have an initial PR where I had removed all references for FSUtils and 
CommonFSUtils, also added those to forbidden APIs.

 

While going through this, I realise there are other references to IA Private 
interfaces, so we may need to look at some more fancy maven plugin that could 
detect references to the annotation as a definitive solution. 

> [hbase-operator-tools] hbck2 filesystem fails against hbase-2.3.x
> -----------------------------------------------------------------
>
>                 Key: HBASE-24793
>                 URL: https://issues.apache.org/jira/browse/HBASE-24793
>             Project: HBase
>          Issue Type: Bug
>          Components: hbck2
>            Reporter: Michael Stack
>            Priority: Major
>
> {code:java}
> 15:23:15.323 [main] INFO  
> org.apache.hadoop.hbase.client.ConnectionImplementation - Closing master 
> protocol: MasterService
> Exception in thread "main" java.lang.NoSuchMethodError: 
> 'org.apache.hadoop.fs.Path 
> org.apache.hadoop.hbase.util.FSUtils.getRootDir(org.apache.hadoop.conf.Configuration)'
>       at org.apache.hbase.FileSystemFsck.<init>(FileSystemFsck.java:49)
>       at org.apache.hbase.HBCK2.doCommandLine(HBCK2.java:720)
>       at org.apache.hbase.HBCK2.run(HBCK2.java:631)
>       at org.apache.hadoop.util.ToolRunner.run(ToolRunner.java:76)
>       at org.apache.hadoop.util.ToolRunner.run(ToolRunner.java:90)
>       at org.apache.hbase.HBCK2.main(HBCK2.java:865) {code}
>  
> If build hbase-operator-tools against hbase-2.3.x its fine again. Could try 
> putting pack the method in hbase-2.3.x or its probably worth a new release of 
> hbase-operator-tools (last was 2018 for 1.0.0) but then it wouldn't work 
> against 2.1 (but 2.1 is EOL'd so ok)? Probably wouldn't work against 2.2 then 
> so maybe put back the method for 2.3?



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to