Mailing-List: contact hama-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hama-dev@incubator.apache.org
Message-ID: <21213564.1220837564495.JavaMail.jira@brutus>
Date: Sun, 7 Sep 2008 18:32:44 -0700 (PDT)
From: "Edward J. Yoon (JIRA)" <jira@apache.org>
To: hama-dev@incubator.apache.org
Subject: [jira] Updated: (HAMA-39) Defining exception policies
In-Reply-To: <1054580720.1219325684202.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Edward J. Yoon updated HAMA-39:
-------------------------------

    Status: Open  (was: Patch Available)

> Defining exception policies 
> ----------------------------
>
>                 Key: HAMA-39
>                 URL: https://issues.apache.org/jira/browse/HAMA-39
>             Project: Hama
>          Issue Type: Improvement
>          Components: interface
>            Reporter: Edward J. Yoon
>            Assignee: Edward J. Yoon
>             Fix For: 0.1.0
>
>         Attachments: HAMA-39.patch
>
>
> Each operations should have a throws clause.
> ----
> In class AbstractMatrix, the exception will be catch to call only LOG.error.
> I would like to discuss a bit more on this issue that how the system
> should do when an exception is thrown.
> But I don't think only logging an error is not enough.
> 1. re-throw the exception. This needs changes of the interface,
> probably we could have the new ComputationException class, or
> something.
> 2. throw a runtime expection, and of course JVM will die here.
> Regards,
> Chanwit

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.