hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Haohui Mai (JIRA)" <j...@apache.org>
Subject [jira] [Moved] (HDFS-9301) HDFS clients can't construct HdfsConfiguration instances
Date Fri, 23 Oct 2015 21:49:28 GMT

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

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

        Key: HDFS-9301  (was: HADOOP-12506)
    Project: Hadoop HDFS  (was: Hadoop Common)

> HDFS clients can't construct HdfsConfiguration instances
> --------------------------------------------------------
>
>                 Key: HDFS-9301
>                 URL: https://issues.apache.org/jira/browse/HDFS-9301
>             Project: Hadoop HDFS
>          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)

Mime
View raw message