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

ASF GitHub Bot commented on TWILL-180:
--------------------------------------

GitHub user chtyim opened a pull request:

    https://github.com/apache/twill/pull/54

    (TWILL-180) Reflects YARN application completion status via TwillController

    

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/chtyim/twill feature/TWILL-180

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/twill/pull/54.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #54
    
----
commit 0e6fd06e4659049dfc335ded9b12a87654de2bda
Author: Terence Yim <cht...@apache.org>
Date:   2017-04-04T06:38:58Z

    (TWILL-180) Reflects YARN application completion status via TwillController

----


> TwillController.onTerminated() should pass the exit status of the app to the 
> callback
> -------------------------------------------------------------------------------------
>
>                 Key: TWILL-180
>                 URL: https://issues.apache.org/jira/browse/TWILL-180
>             Project: Apache Twill
>          Issue Type: Improvement
>          Components: api, yarn
>    Affects Versions: 0.7.0-incubating
>            Reporter: Andreas Neumann
>            Assignee: Terence Yim
>             Fix For: 0.11.0
>
>
> Listening to this callback, a client can only find out whether an app has 
> terminated, but now how. That makes it hard to distinguish error scenarios: 
> Was the app killed by the user? Did it fail? Or did it successfully complete? 
> There should be an easy way for the client to find out.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Reply via email to