Mailing-List: contact issues-help@ignite.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@ignite.apache.org
Date: Wed, 10 Aug 2016 07:28:20 +0000 (UTC)
From: "Vladimir Ozerov (JIRA)" <jira@apache.org>
To: issues@ignite.apache.org
Message-ID: <JIRA.12996180.1470814043000.269378.1470814100566@Atlassian.JIRA>
In-Reply-To: <JIRA.12996180.1470814043000@Atlassian.JIRA>
References: <JIRA.12996180.1470814043000@Atlassian.JIRA> <JIRA.12996180.1470814043382@arcas>
Subject: [jira] [Created] (IGNITE-3668) IGFS: Local secondary: Review all
 "throw new IOException" places.
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Wed, 10 Aug 2016 07:28:22 -0000

Vladimir Ozerov created IGNITE-3668:
---------------------------------------

             Summary: IGFS: Local secondary: Review all "throw new IOException" places.
                 Key: IGNITE-3668
                 URL: https://issues.apache.org/jira/browse/IGNITE-3668
             Project: Ignite
          Issue Type: Sub-task
          Components: IGFS
    Affects Versions: 1.7
            Reporter: Vladimir Ozerov
            Assignee: Taras Ledkov
             Fix For: 1.8


We have several places in {{LocalIgfsSecondaryFileSystem}} where {{IOException}} is thrown. This is not correct, because:
1) Exception must be specific. E.g. "path-not-found-exception".
2) It doesn't make sense to throw {{IOException}} and cast it to {{IgfsException}} immediately.

Also we should not throw {{IgniteException}}. Proper {{IgfsException}} must be thrown.

Let's review all these places and replace {{IOException}} with proper {{IgfsException}} inheritor. 

Successful implementation should not introduce any new test failures.


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