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

Hadoop QA commented on YARN-5127:
---------------------------------

| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 0m 0s 
{color} | {color:blue} Docker mode activated. {color} |
| {color:red}-1{color} | {color:red} patch {color} | {color:red} 0m 4s {color} 
| {color:red} YARN-5127 does not apply to trunk. Rebase required? Wrong Branch? 
See https://wiki.apache.org/hadoop/HowToContribute for help. {color} |
\\
\\
|| Subsystem || Report/Notes ||
| JIRA Patch URL | 
https://issues.apache.org/jira/secure/attachment/12806247/YARN-5127.v1.patch |
| JIRA Issue | YARN-5127 |
| Console output | 
https://builds.apache.org/job/PreCommit-YARN-Build/11702/console |
| Powered by | Apache Yetus 0.2.0   http://yetus.apache.org |


This message was automatically generated.



> Expose ExecutionType in Container api record
> --------------------------------------------
>
>                 Key: YARN-5127
>                 URL: https://issues.apache.org/jira/browse/YARN-5127
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>            Reporter: Arun Suresh
>            Assignee: Hitesh Sharma
>         Attachments: YARN-5127.v1.patch
>
>
> Currently the ExecutionType of the Container returned as a response to the 
> allocate call is contained in the {{ContinerTokenIdentifier}} which is 
> encoded into the ContainerToken.
> Unfortunately, the client would need to decode the returned token to access 
> the ContainerTokenIdentifier, which probably should not be allowed.
> This JIRA proposes to add a {{getExecutionType()}} method in the container 
> record.



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

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to