[jira] [Updated] (REEF-1415) Set AsError to TaskExceptionMissingException on FailedTask for FailedEvaluators

["Andrew Chung (JIRA)" <ji...@apache.org>]

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

Andrew Chung updated REEF-1415:
-------------------------------
    Summary: Set AsError to TaskExceptionMissingException on FailedTask for FailedEvaluators  (was: Deprecate JavaTaskException and set AsError to TaskExceptionMissingException on FailedTask for FailedEvaluators)

> Set AsError to TaskExceptionMissingException on FailedTask for FailedEvaluators
> -------------------------------------------------------------------------------
>
>                 Key: REEF-1415
>                 URL: https://issues.apache.org/jira/browse/REEF-1415
>             Project: REEF
>          Issue Type: Bug
>          Components: REEF.NET, REEF.NET Driver
>            Reporter: Andrew Chung
>            Assignee: Andrew Chung
>
> Non-existent Task Exceptions can occur when an Evaluator fails unexpectedly. The Task itself does not throw an Exception, so the FailedTask therefore should not contain an Exception object.
> Java Task Exceptions are currently generated when {{AvroFailedTask.Data}} is set to a {{null}} byte array. Provided that the Avro schema of FailedTask does not union with {{null}}, this will never occur.
> Now that C# Task Exceptions support serialization such that even when a user's Exception is not serializable we wrap a {{NonSerializableTaskException}} around it, we can assume that an empty {{AvroFailedTask.Data}} only occurs when the Evaluator fails. We should thus return {{null}} when the user calls {{AsError()}} on a {{FailedTask}} that comes from a {{FailedEvaluator}}.



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