Mailing-List: contact issues-help@geode.incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@geode.incubator.apache.org
Date: Wed, 4 May 2016 17:29:12 +0000 (UTC)
From: "Dan Smith (JIRA)" <jira@apache.org>
To: issues@geode.incubator.apache.org
Message-ID: <JIRA.12965036.1462382904000.110613.1462382952949@Atlassian.JIRA>
In-Reply-To: <JIRA.12965036.1462382904000@Atlassian.JIRA>
References: <JIRA.12965036.1462382904000@Atlassian.JIRA> <JIRA.12965036.1462382904274@arcas>
Subject: [jira] [Created] (GEODE-1348) Exceptions thrown from Functions are
 inconsistently wrapped with FunctionException
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Wed, 04 May 2016 17:29:17 -0000

Dan Smith created GEODE-1348:
--------------------------------

             Summary: Exceptions thrown from Functions are inconsistently wrapped with FunctionException
                 Key: GEODE-1348
                 URL: https://issues.apache.org/jira/browse/GEODE-1348
             Project: Geode
          Issue Type: Bug
          Components: functions
            Reporter: Dan Smith


I wrote some tests for how exceptions throw within a function are returned to the executor of the function.

What I'm seeing is that how the function is returned varies based on the topology and region type used. Specifically, in almost all cases an exception thrown from within a Function is wrapped in a FunctionException. But when using onRegion with a partitioned region from an accessor, the exception is not wrapped in a FunctionException but is instead thrown directly.

Exceptions should be handled consistently. Since most cases seem to wrap the exception in a FunctionException, the PR accessor case probably should too.


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