[jira] [Moved] (HADOOP-12506) HDFS clients can't construct HdfsConfiguration instances

["Haohui Mai (JIRA)" <ji...@apache.org>]

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

Haohui Mai moved HDFS-9241 to HADOOP-12506:
-------------------------------------------

    Component/s:     (was: hdfs-client)
            Key: HADOOP-12506  (was: HDFS-9241)
        Project: Hadoop Common  (was: Hadoop HDFS)

> HDFS clients can't construct HdfsConfiguration instances
> --------------------------------------------------------
>
>                 Key: HADOOP-12506
>                 URL: https://issues.apache.org/jira/browse/HADOOP-12506
>             Project: Hadoop Common
>          Issue Type: Bug
>            Reporter: Steve Loughran
>            Assignee: Mingliang Liu
>         Attachments: HDFS-9241.000.patch, HDFS-9241.001.patch, HDFS-9241.002.patch, HDFS-9241.003.patch, HDFS-9241.004.patch, HDFS-9241.005.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)