[ https://issues.apache.org/jira/browse/HADOOP-8356?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13268375#comment-13268375 ]
Hudson commented on HADOOP-8356: -------------------------------- Integrated in Hadoop-Mapreduce-trunk #1069 (See [https://builds.apache.org/job/Hadoop-Mapreduce-trunk/1069/]) HADOOP-8356. FileSystem service loading mechanism should print the FileSystem impl it is failing to load (tucu) (Revision 1333744) Result = SUCCESS tucu : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1333744 Files : * /hadoop/common/trunk/hadoop-common-project/hadoop-common/CHANGES.txt * /hadoop/common/trunk/hadoop-common-project/hadoop-common/src/main/java/org/apache/hadoop/fs/FileSystem.java > FileSystem service loading mechanism should print the FileSystem impl it is > failing to load > ------------------------------------------------------------------------------------------- > > Key: HADOOP-8356 > URL: https://issues.apache.org/jira/browse/HADOOP-8356 > Project: Hadoop Common > Issue Type: Improvement > Components: fs > Affects Versions: 2.0.0 > Reporter: Alejandro Abdelnur > Assignee: Alejandro Abdelnur > Fix For: 2.0.0 > > Attachments: HADOOP-8356.patch > > > If by mistake somebody adds a FileSystem implementation to the service > definition that is not serviceloader friendly (it does not override the > getScheme() method) or adds to the classpath an older one defined in the > service definition, the exception thrown should print out the FileSystem > class failing to load. -- 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