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 2015/12/10 09:53:11 UTC

[jira] [Updated] (IGNITE-1638) IGFS: Review IgfsImpl.checkConflictWithPrimary() method.

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

Vladimir Ozerov updated IGNITE-1638:
------------------------------------
    Fix Version/s:     (was: 1.5)
                   1.6

> IGFS: Review IgfsImpl.checkConflictWithPrimary() method.
> --------------------------------------------------------
>
>                 Key: IGNITE-1638
>                 URL: https://issues.apache.org/jira/browse/IGNITE-1638
>             Project: Ignite
>          Issue Type: Task
>          Components: hadoop
>    Affects Versions: ignite-1.4
>            Reporter: Vladimir Ozerov
>            Assignee: Ivan Veselovsky
>             Fix For: 1.6
>
>
> This method looks very suspicious to me. It checks whether secondary file system contains any file under the same path as IGFS primary direcotry. If yes - an exception is thrown.
> But why? What is the use case we are trying to resolve with this?
> We need to re-think this approach and decide whether to leave it or remove it.



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