[
https://issues.apache.org/jira/browse/HDFS-9241?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14966609#comment-14966609
]
Steve Loughran commented on HDFS-9241:
--------------------------------------
I like this. I'll still have to move my code off DFSConfigKeys, which means
some inlining of constants, but at least the critical issue, getting those
hdfs-site and hdfs-default XML resources loaded will be addressed. That's the
thing that would have really caused problems.
I'll leave for others to give a final vote, but I'm personally +1 here
> HDFS clients can't construct HdfsConfiguration instances
> --------------------------------------------------------
>
> Key: HDFS-9241
> URL: https://issues.apache.org/jira/browse/HDFS-9241
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: hdfs-client
> Reporter: Steve Loughran
> Assignee: Mingliang Liu
> Attachments: HDFS-9241.000.patch, HDFS-9241.001.patch
>
>
> the changes for the hdfs client classpath make instantiating
> {{HdfsConfiguration}} from the client impossible; it only lives server side.
> This breaks any app which creates one.
> I know people will look at the {{@Private}} tag and say "don't do that then",
> but it's worth considering precisely why I, at least, do this: it's the only
> way to guarantee that the hdfs-default and hdfs-site resources get on the
> classpath, including all the security settings. It's precisely the use case
> which {{HdfsConfigurationLoader.init();}} offers internally to the hdfs code.
> What am I meant to do now?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
