hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hadoop QA (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-2615) ClientToAMTokenIdentifier and DelegationTokenIdentifier should allow extended fields
Date Thu, 02 Oct 2014 15:13:35 GMT

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

Hadoop QA commented on YARN-2615:
---------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12672553/YARN-2615-v2.patch
  against trunk revision c7cee9b.

    {color:green}+1 @author{color}.  The patch does not contain any @author tags.

    {color:green}+1 tests included{color}.  The patch appears to include 6 new or modified
test files.

    {color:red}-1 javac{color:red}.  The patch appears to cause the build to fail.

Console output: https://builds.apache.org/job/PreCommit-YARN-Build/5237//console

This message is automatically generated.

> ClientToAMTokenIdentifier and DelegationTokenIdentifier should allow extended fields
> ------------------------------------------------------------------------------------
>
>                 Key: YARN-2615
>                 URL: https://issues.apache.org/jira/browse/YARN-2615
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>            Reporter: Junping Du
>            Assignee: Junping Du
>            Priority: Blocker
>         Attachments: YARN-2615-v2.patch, YARN-2615.patch
>
>
> As three TokenIdentifiers get updated in YARN-668, ClientToAMTokenIdentifier and DelegationTokenIdentifier
should also be updated in the same way to allow fields get extended in future.



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

Mime
View raw message