[
https://issues.apache.org/jira/browse/HADOOP-9041?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13533109#comment-13533109
]
Radim Kolar commented on HADOOP-9041:
-------------------------------------
If there is an problem in FileSystem.getFileSystemClass("file", conf); then you
will catch that exception later in correct code path, where it is called,
expected and processed. Here it is just initializer.
You might be interested in different filesystem "hdfs" and thus throwing an
exception because "file" failed load increases complexity of initializer
exception handling in caller.
> FileSystem initialization can go into infinite loop
> ---------------------------------------------------
>
> Key: HADOOP-9041
> URL: https://issues.apache.org/jira/browse/HADOOP-9041
> Project: Hadoop Common
> Issue Type: Bug
> Components: fs
> Affects Versions: 2.0.2-alpha
> Reporter: Radim Kolar
> Assignee: Radim Kolar
> Priority: Critical
> Attachments: fsinit2.txt, fsinit3.txt, fsinit4.txt, fsinit-unit.txt,
> fstest.groovy, HADOOP-9041.patch, HADOOP-9041.patch, TestFileSystem.java
>
>
> More information is there: https://jira.springsource.org/browse/SHDP-111
> Referenced source code from example is:
> https://github.com/SpringSource/spring-hadoop/blob/master/src/main/java/org/springframework/data/hadoop/configuration/ConfigurationFactoryBean.java
> from isolating that cause it looks like if you register:
> org.apache.hadoop.fs.FsUrlStreamHandlerFactory before calling
> FileSystem.loadFileSystems() then it goes into infinite loop.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
