You are viewing a plain text version of this content. The canonical link for it is here.
Posted to hdfs-issues@hadoop.apache.org by "Steve Loughran (JIRA)" <ji...@apache.org> on 2015/10/14 16:49:05 UTC

[jira] [Updated] (HDFS-9241) HDFS clients can't construct HdfsConfiguration instances

     [ https://issues.apache.org/jira/browse/HDFS-9241?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Steve Loughran updated HDFS-9241:
---------------------------------
    Affects Version/s: 3.0.0
          Component/s: hdfs-client

> 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
>    Affects Versions: 3.0.0
>            Reporter: Steve Loughran
>
> 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)