[HDFS-9301] HDFS clients can't construct HdfsConfiguration instances

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 2.8.0, 3.0.0-alpha1
• Hadoop Flags: Reviewed
• Assignee: Mingliang Liu
• Reporter: Steve Loughran
• Created: 14/Oct/15 14:48
• Updated: 30/Aug/16 01:24
• Resolved: 23/Oct/15 21:54

Description

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?

Issue Links

• duplicates: HDFS-9202 Deprecation cases are not handled in hadoop-hdfs-client#DistributedFileSystem
• is broken by: HDFS-6200 Create a separate jar for hdfs-client
• is related to: HDFS-10610 DfsClient doesn't add hdfs-site.xml as a resource