[ https://issues.apache.org/jira/browse/HDFS-9241?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14961557#comment-14961557 ]
Mingliang Liu commented on HDFS-9241: ------------------------------------- {quote} Old applications can still depend on hadoop-hdfs and nothing will break. However, the application might need to change a couple lines of code if it only wants to depend on hadoop-hdfs-client. {quote} It makes sense to me. Do you think we need to make {{HdfsConfigurationLoader}} public so that code depending on {{hadoop-hdfs-client}} is able to load the default resource forcefully (in case)? > 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 > > > 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)