[
https://issues.apache.org/jira/browse/HBASE-4510?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13132116#comment-13132116
]
Hudson commented on HBASE-4510:
-------------------------------
Integrated in HBase-TRUNK #2346 (See
[https://builds.apache.org/job/HBase-TRUNK/2346/])
HBASE-4510 Check and workaround usage of internal HDFS APIs in HBase
stack :
Files :
* /hbase/trunk/CHANGES.txt
* /hbase/trunk/src/main/java/org/apache/hadoop/hbase/util/FSHDFSUtils.java
* /hbase/trunk/src/main/java/org/apache/hadoop/hbase/util/FSUtils.java
> Check and workaround usage of internal HDFS APIs in HBase
> ---------------------------------------------------------
>
> Key: HBASE-4510
> URL: https://issues.apache.org/jira/browse/HBASE-4510
> Project: HBase
> Issue Type: Task
> Affects Versions: 0.94.0
> Reporter: Harsh J
> Assignee: Harsh J
> Fix For: 0.92.0
>
> Attachments: HBASE-4510.patch
>
>
> HBase isn't seemingly compiling anymore on 0.23 after the HDFS-1620 naming
> refactorings were carried out.
> Two solutions:
> * We use new classnames. This breaks HBase's backward compatibility with
> older Hadoop releases (is that a concern with future releases?)
> * HBase gets its own sets of constants as the upstream one is not marked for
> public usage. This needs a little more maintenance on HBases' side.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
