hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jitendra Nath Pandey (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HADOOP-6661) User document for UserGroupInformation.doAs
Date Wed, 02 Jun 2010 21:37:37 GMT

    [ https://issues.apache.org/jira/browse/HADOOP-6661?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12874808#action_12874808

Jitendra Nath Pandey commented on HADOOP-6661:

test patch results

     [exec] -1 overall.  
     [exec]     +1 @author.  The patch does not contain any @author tags.
     [exec]     -1 tests included.  The patch doesn't appear to include any new or modified
     [exec]                         Please justify why no new tests are needed for this patch.
     [exec]                         Also please list what manual steps were performed to verify
this patch.
     [exec]     +1 javadoc.  The javadoc tool did not generate any warning messages.
     [exec]     +1 javac.  The applied patch does not increase the total number of javac compiler
     [exec]     +1 findbugs.  The patch does not introduce any new Findbugs warnings.
     [exec]     +1 release audit.  The applied patch does not increase the total number of
release audit warnings.

No tests added or modified because this patch adds a user document.

> User document for UserGroupInformation.doAs
> -------------------------------------------
>                 Key: HADOOP-6661
>                 URL: https://issues.apache.org/jira/browse/HADOOP-6661
>             Project: Hadoop Common
>          Issue Type: Improvement
>            Reporter: Jitendra Nath Pandey
>            Assignee: Jitendra Nath Pandey
>         Attachments: HADOOP-6661-y20.1.patch, HADOOP-6661-y20.2.patch, HADOOP-6661.1.patch,
> A user document should be added for secure impersonation feature. The document should
cover a code example about how  UserGroupInformation.doAs should be used for secure impersonation.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message