[
https://issues.apache.org/jira/browse/HADOOP-7549?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13087258#comment-13087258
]
Suresh Srinivas commented on HADOOP-7549:
-----------------------------------------
bq. Maybe we shouldn't say config loading is deprecated, and we should remove
the warning I'm putting there.
That is what I was getting at
bq. Regarding mapreduce, would you point me to the place where that happens?
grep fs.*impl in java files
Given that we cannot deprecate the config based mechanism, which in addition to
the mechanism you are proposing, allows changing FileSystem implementation
during run time, why do we need this scheme?
> Use JDK ServiceLoader mechanism to find FileSystem implementations
> ------------------------------------------------------------------
>
> Key: HADOOP-7549
> URL: https://issues.apache.org/jira/browse/HADOOP-7549
> Project: Hadoop Common
> Issue Type: Improvement
> Components: fs
> Affects Versions: 0.23.0
> Reporter: Alejandro Abdelnur
> Assignee: Alejandro Abdelnur
> Fix For: 0.23.0
>
> Attachments: HADOOP-7549v1.patch
>
>
> Currently configuring FileSystem implementations must be done by declaring
> the FileSystem class in the Hadoop configuration files (core-default.xml,
> ...).
> Using JDK ServiceLoader mechanism this configuration step can be avoided.
> Adding the JAR file with the additional FileSystem implementation would
> suffice.
> This is similar to what is being proposed for compression codecs
> (HADOOP-7350).
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
