[
https://issues.apache.org/jira/browse/HDFS-13847?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16589101#comment-16589101
]
Xiao Chen commented on HDFS-13847:
----------------------------------
As a side note, also found the {{clear}} method had some comments from
HDFS-11633, more details
[here|https://issues.apache.org/jira/browse/HDFS-11633?focusedCommentId=15961250&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-15961250].
Now that HDFS-7337 is done, we can finish the TODO in another jira.
> Clean up ErasureCodingPolicyManager
> -----------------------------------
>
> Key: HDFS-13847
> URL: https://issues.apache.org/jira/browse/HDFS-13847
> Project: Hadoop HDFS
> Issue Type: Improvement
> Components: erasure-coding
> Affects Versions: 3.0.0
> Reporter: Xiao Chen
> Priority: Major
>
> {{ErasureCodingPolicyManager}} class is declared as LimitedPrivate for HDFS.
> This doesn't seem to make sense, as I have checked all its usages are
> strictly within hadoop-hdfs project.
> According to our [compat
> guide|http://hadoop.apache.org/docs/r3.1.0/hadoop-project-dist/hadoop-common/Compatibility.html]:
> {quote}
> Within a component Hadoop developers are free to use Private and Limited
> Private APIs,
> {quote}
> We should tune this down to just Private.
> This is identified because an internal testing marked HDFS-13772 as
> incompatible, due to the method signature changes on the ECPM class.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
