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

Rich Haase commented on YARN-4207:
----------------------------------

This looks like a pretty trivial change.  Adding an additional value to the 
o.a.h.yarn.records.FinalApplicationStatus enum.  In a quick search I didn't see 
anything downstream within Hadoop that would be impacted by such a patch.  If 
no one else is working on this JIRA and the approach I've described is 
acceptable I will put together a patch.




> Add a non-judgemental YARN app completion status
> ------------------------------------------------
>
>                 Key: YARN-4207
>                 URL: https://issues.apache.org/jira/browse/YARN-4207
>             Project: Hadoop YARN
>          Issue Type: Improvement
>            Reporter: Sergey Shelukhin
>
> For certain applications, it doesn't make sense to have SUCCEEDED or FAILED 
> end state. For example, Tez sessions may include multiple DAGs, some of which 
> have succeeded and some have failed; there's no clear status for the session 
> both logically and from user perspective (users are confused either way). 
> There needs to be a status not implying success or failure, such as 
> "done"/"ended"/"finished".



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

Reply via email to