Mailing-List: contact hdfs-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hdfs-dev@hadoop.apache.org
Date: Wed, 14 Oct 2015 14:49:05 +0000 (UTC)
From: "Steve Loughran (JIRA)" <jira@apache.org>
To: hdfs-dev@hadoop.apache.org
Message-ID: <JIRA.12904894.1444834103000.37423.1444834145175@Atlassian.JIRA>
In-Reply-To: <JIRA.12904894.1444834103000@Atlassian.JIRA>
References: <JIRA.12904894.1444834103000@Atlassian.JIRA>
 <JIRA.12904894.1444834103278@arcas>
Subject: [jira] [Created] (HDFS-9241) HDFS clients can't construct
 HdfsConfiguration instances
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Steve Loughran created HDFS-9241:
------------------------------------

             Summary: 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
            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)