[
https://issues.apache.org/jira/browse/HDFS-8345?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14546173#comment-14546173
]
Arpit Agarwal commented on HDFS-8345:
-------------------------------------
bq. That's not so bad. Is there a reason not to include a convenience method
that just takes a BlockStoragePolicySpi object directly?
That doesn't sound useful enough to introduce one more FileSystem API. Can you
think of an example where the extra API call would simplify application code?
bq. Can you point me to the exposure? BlockStoragePolicy is IA.Private, and I
would expect we can use covariant return types to make a source-compatible
update.
It was tagged IA.Private but returned via a LimitedPrivate interface,
unfortunate as that is. Changing the name, package or public interface of
BlockStoragePolicy would technically be incompatible. However if you suggest a
better name for the new interface I'd be happy to change it.
bq. The one in the docs:
http://hadoop.apache.org/docs/current/hadoop-project-dist/hadoop-common/filesystem/index.html
Okay let me file a separate Jira for that.
> Storage policy APIs must be exposed via the FileSystem interface
> ----------------------------------------------------------------
>
> Key: HDFS-8345
> URL: https://issues.apache.org/jira/browse/HDFS-8345
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: hdfs-client
> Affects Versions: 2.7.0
> Reporter: Arpit Agarwal
> Assignee: Arpit Agarwal
> Labels: BB2015-05-TBR
> Attachments: HDFS-8345.01.patch, HDFS-8345.02.patch,
> HDFS-8345.03.patch, HDFS-8345.04.patch, HDFS-8345.05.patch, HDFS-8345.06.patch
>
>
> The storage policy APIs are not exposed via FileSystem. Since
> DistributedFileSystem is tagged as LimitedPrivate we should expose the APIs
> through FileSystem for use by other applications.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
