Mailing-List: contact dev-help@reef.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@reef.apache.org
Date: Mon, 19 Sep 2016 16:14:20 +0000 (UTC)
From: "Julia (JIRA)" <jira@apache.org>
To: dev@reef.apache.org
Message-ID: <JIRA.13005557.1474060020000.606613.1474301660489@Atlassian.JIRA>
In-Reply-To: <JIRA.13005557.1474060020000@Atlassian.JIRA>
References: <JIRA.13005557.1474060020000@Atlassian.JIRA> <JIRA.13005557.1474060020073@arcas>
Subject: [jira] [Commented] (REEF-1565) Make Context accessible from task
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Mon, 19 Sep 2016 16:14:22 -0000


    [ https://issues.apache.org/jira/browse/REEF-1565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15503878#comment-15503878 ] 

Julia commented on REEF-1565:
-----------------------------

I see your point. Context and Task can inject the same singleton even context itself is not injected. I will close the PR. 

> Make Context accessible from task
> ---------------------------------
>
>                 Key: REEF-1565
>                 URL: https://issues.apache.org/jira/browse/REEF-1565
>             Project: REEF
>          Issue Type: Task
>            Reporter: Julia
>            Assignee: Julia
>              Labels: FT
>
> For fault tolerant, states should be saved at context level so that when the task is resubmitted, update task host would be able to restore the state from the context. 
> Currently, we start task from context. But inside task we are not able to access context. As ContextRuntime could have multiple instances, it is not created by injection. 
> This Jira is to make Task able to inject context where the task is running on. This is the first step for the state management. 


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