[
https://issues.apache.org/jira/browse/HDFS-3263?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13255047#comment-13255047
]
Daryn Sharp commented on HDFS-3263:
-----------------------------------
I've only skimmed the patch. I'm curious if there's a reason why it seems to
be hard coding keys instead of using the keys from
{{CommonConfigurationKeysPublic}}, etc? Ex. "fs.default.name", which appears
to be deprecated, instead of {{FS_DEFAULT_NAME_KEY}}. Also, why does it need
to hardcode the resource files for {{Configuration}}?
> HttpFS should read HDFS config from Hadoop site.xml files
> ---------------------------------------------------------
>
> Key: HDFS-3263
> URL: https://issues.apache.org/jira/browse/HDFS-3263
> Project: Hadoop HDFS
> Issue Type: Improvement
> Affects Versions: 2.0.0
> Reporter: Alejandro Abdelnur
> Assignee: Alejandro Abdelnur
> Fix For: 2.0.0
>
> Attachments: HDFS-3263.patch
>
>
> Currently HttpFS reads HDFS client configuration from the httfs-site.xml from
> any property of the form 'httpfs.hadoop.conf:HADOOP_PROPERTY'
> This is a bit inconvenient.
> Instead we should support a single property 'httpfs.hadoop.configuration.dir'
> that can be pointed to HADOOP conf/ dir and the core-site.xml and
> hdfs-site.xml files would be read from there.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
