You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Vladimir Ozerov (JIRA)" <ji...@apache.org> on 2016/01/08 09:48:39 UTC

[jira] [Resolved] (IGNITE-2340) Throw sensible error from IgniteHadoopFileSystem if real file system is not IgniteHadoopIgfsSecondaryFileSystem

     [ https://issues.apache.org/jira/browse/IGNITE-2340?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Vladimir Ozerov resolved IGNITE-2340.
-------------------------------------
    Resolution: Fixed

> Throw sensible error from IgniteHadoopFileSystem if real file system is not IgniteHadoopIgfsSecondaryFileSystem
> ---------------------------------------------------------------------------------------------------------------
>
>                 Key: IGNITE-2340
>                 URL: https://issues.apache.org/jira/browse/IGNITE-2340
>             Project: Ignite
>          Issue Type: Task
>          Components: hadoop
>    Affects Versions: ignite-1.4
>            Reporter: Vladimir Ozerov
>            Assignee: Vladimir Ozerov
>              Labels: important
>             Fix For: 1.6
>
>
> Consider the following scenario:
> 1) User configures some custom secondary file system;
> 2) Some paths are set to PROXY mode (e.g. default modes);
> 3) User instantiates IgniteHadoopFileSystem somewhere else. 
> Result:
> IgniteHadoopFileSystem notices PROXY paths and tries to get FileSystem factory from handshake request, but it is null. As a result, NPE is thrown a moment later.
> Proposed fix:
> If factory is null. we must throw an exception and advise user to set IgniteHadoopIgfsSecondaryFileSystem as secondary file system.in IGFS configuration.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)