You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@reef.apache.org by "Julia (JIRA)" <ji...@apache.org> on 2016/05/10 18:36:12 UTC
[jira] [Resolved] (REEF-1286) Forward .NET Exceptions from the
Evaluator to the Driver
[ https://issues.apache.org/jira/browse/REEF-1286?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Julia resolved REEF-1286.
-------------------------
Resolution: Fixed
Fix Version/s: 0.15
Resolved via https://github.com/apache/reef/pull/988
> Forward .NET Exceptions from the Evaluator to the Driver
> ---------------------------------------------------------
>
> Key: REEF-1286
> URL: https://issues.apache.org/jira/browse/REEF-1286
> Project: REEF
> Issue Type: Improvement
> Components: REEF.NET, REEF.NET Driver, REEF.NET Evaluator
> Reporter: Julia
> Assignee: Andrew Chung
> Labels: FT
> Fix For: 0.15
>
>
> Currently, when we pass .Net exceptions from Evaluator to java Driver, we don't set exception details such as cause, description, etc. In stead, we serialize Exception.ToString() that doesn't have individual properties.
> We should set exception details in protobuffer before serialize it over from evaluator to driver, so that we would be able to get the details from the failed object in handlers.
> We then need to make those properties accessible over the bridge so that we can access them in IFailedEvaluator, IFailedContext and IFailedTask cases.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)