[
https://issues.apache.org/jira/browse/HDFS-9301?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14974981#comment-14974981
]
Steve Loughran commented on HDFS-9301:
--------------------------------------
OK, I can verify that with this patch, my code compiles again.
However, I still think we ought to consider keeping hadoop-client pom depend on
hadoop-hdfs, just as it pulls in other stuff (jets3t) that we don't really
like. Then the hadoop-lean client can stay lean, and we could even have a
policy for this "we can remove dependency JARs if we feel like it"
> 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
> Fix For: 2.8.0
>
> 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)
