[
https://issues.apache.org/jira/browse/HADOOP-16102?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16767390#comment-16767390
]
Steve Loughran commented on HADOOP-16102:
-----------------------------------------
I'm actually reluctant to make changes here.
The problem is that the FileSystem.getScheme() is invoked as part of the FS
Service load mechanism, without initializing the filesystem. At which point,
there's no {{fs}} to pass this call on.
We could be clever and say "united => "filter"" but once inited switch to the
inner scheme, but there's a risk of that causing different confusion as the
scheme of an FS changes during its life. I don't know what the consequences
will be there: if anyone is expecting it to be a constant for use in a map of
some form, they'll be surprised.
Now, FilterFS isn't registered for discovery in
hadoop-common-project/hadoop-common/src/main/resources/META-INF/services/org.apache.hadoop.fs.FileSystem,
so FileSystem isn't mapping filter -> FilterFileSystem.class, but I don't know
what is happening elsewhere.
> FilterFileSystem does not implement getScheme
> ---------------------------------------------
>
> Key: HADOOP-16102
> URL: https://issues.apache.org/jira/browse/HADOOP-16102
> Project: Hadoop Common
> Issue Type: Bug
> Components: fs
> Reporter: Todd Owen
> Priority: Minor
>
> Calling {{getScheme}} on a {{FilterFileSystem}} throws
> {{UnsupportedOperationException}}, which is the default provided by the base
> class. Instead, it should return the scheme of the underlying ("filtered")
> filesystem.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
