Mailing-List: contact dev-help@reef.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@reef.apache.org
Date: Sat, 5 Dec 2015 23:44:10 +0000 (UTC)
From: "Andrew Chung (JIRA)" <jira@apache.org>
To: dev@reef.apache.org
Message-ID: <JIRA.12848891.1437743615000.281117.1449359050945@Atlassian.JIRA>
In-Reply-To: <JIRA.12848891.1437743615000@Atlassian.JIRA>
References: <JIRA.12848891.1437743615000@Atlassian.JIRA>
 <JIRA.12848891.1437743615371@arcas>
Subject: [jira] [Commented] (REEF-502) Support Vortex Tasklet(s)
 cancellation by user
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Andrew Chung commented on REEF-502:
-----------------------------------

PR is out, please have a look!
Note the assumptions on the PR: Tasklet ID is unique, and each tasklet only matches to one VortexFuture. We can make changes to accommodate duplicate tasklets once REEF-500 is shaped up. Thanks!

> Support Vortex Tasklet(s) cancellation by user
> ----------------------------------------------
>
>                 Key: REEF-502
>                 URL: https://issues.apache.org/jira/browse/REEF-502
>             Project: REEF
>          Issue Type: Sub-task
>          Components: Vortex
>            Reporter: John Yang
>            Assignee: Andrew Chung
>            Priority: Minor
>
> Currently VortexFuture#cancel and VortexFuture#isCancelled throw UnsupportedOperationException. It would be great to implement them. This task is likely to touch on end-to-end Vortex Master-Worker control flow.


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