Mailing-List: contact issues-help@ignite.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@ignite.apache.org
Date: Thu, 21 Jul 2016 10:12:20 +0000 (UTC)
From: "Vladimir Ozerov (JIRA)" <jira@apache.org>
To: issues@ignite.apache.org
Message-ID: <JIRA.12903357.1444310821000.94060.1469095940600@Atlassian.JIRA>
In-Reply-To: <JIRA.12903357.1444310821000@Atlassian.JIRA>
References: <JIRA.12903357.1444310821000@Atlassian.JIRA> <JIRA.12903357.1444310821431@arcas>
Subject: [jira] [Updated] (IGNITE-1638) IGFS: Review
 IgfsImpl.checkConflictWithPrimary() method.
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Thu, 21 Jul 2016 10:12:22 -0000


     [ 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: 1.7

> 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: Vladimir Ozerov
>             Fix For: 1.7
>
>
> 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)