You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@reef.apache.org by "Markus Weimer (JIRA)" <ji...@apache.org> on 2016/03/23 17:12:25 UTC
[jira] [Created] (REEF-1272) Rethink the reporting of ClosedContext
for the root context
Markus Weimer created REEF-1272:
-----------------------------------
Summary: Rethink the reporting of ClosedContext for the root context
Key: REEF-1272
URL: https://issues.apache.org/jira/browse/REEF-1272
Project: REEF
Issue Type: Task
Components: REEF Driver
Reporter: Markus Weimer
Currently, REEF doesn't generate an {{ClosedContext}} / {{IClosedContext}} event for the root context. Instead, the Driver receives an {{ClosedEvaluator}} / {{IClosedEvaluator}}.
This seemed like a good idea at the time as we can't guarantee order between the {{ClosedContext}} and {{ClosedEvaluator}} event. Hence, sending the more significant event makes sense.
However, this choice is troubling because it makes handling of contexts non-uniform, depending on whether it is the root context. Let's use this JIRA to discuss what can or should be done about this. Some ideas:
# Do nothing. The current behavior still makes sense.
# Add the {{ClosedContext}} as a field to {{ClosedEvaluator}}. This is the approach we took in {{FailedEvaluator}}.
# Raise both the {{ClosedContext}} and the {{ClosedEvaluator}} event, but *in order*: Wait for the {{ClosedContext}} event to be handled, then generate the {{ClosedEvaluator}}.
# Drop the {{ClosedEvaluator}} event altogether. Instead, add {{isRootContext()}} to the {{ClosedContext}} event.
Thoughts?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)