[
https://issues.apache.org/jira/browse/HDFS-2412?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13122595#comment-13122595
]
Aaron T. Myers commented on HDFS-2412:
--------------------------------------
I personally do think HDFS-1620 is worth it, and shouldn't be reverted. The
patch Todd's provided is very straight-forward, and should fix things up for
all down-stream projects that might be affected.
My apologies for not realizing that these private constants are referenced in
public APIs when I originally reviewed HDFS-1620. I should have checked for
that.
> Add backwards-compatibility layer for FSConstants
> -------------------------------------------------
>
> Key: HDFS-2412
> URL: https://issues.apache.org/jira/browse/HDFS-2412
> Project: Hadoop HDFS
> Issue Type: Bug
> Affects Versions: 0.23.0
> Reporter: Todd Lipcon
> Assignee: Todd Lipcon
> Priority: Blocker
> Fix For: 0.23.0
>
> Attachments: hdfs-2412.txt
>
>
> HDFS-1620 renamed FSConstants which we believed to be a private class. But
> currently the public APIs for safe-mode and datanode reports depend on
> constants in FSConstants. This is breaking HBase builds against 0.23. This
> JIRA is to provide a backward-compatibility route.
--
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
