You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-issues@hadoop.apache.org by "Jitendra Nath Pandey (JIRA)" <ji...@apache.org> on 2010/04/07 00:17:34 UTC
[jira] Created: (HADOOP-6687) user object in the subject in UGI
should be reused in case of a relogin.
user object in the subject in UGI should be reused in case of a relogin.
-------------------------------------------------------------------------
Key: HADOOP-6687
URL: https://issues.apache.org/jira/browse/HADOOP-6687
Project: Hadoop Common
Issue Type: Bug
Reporter: Jitendra Nath Pandey
In case of a relogin, a new user object is created in the subject. This causes the subject to lose some state for example authentication method. Instead, a new user object should not be added to the subject if one is already present.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (HADOOP-6687) user object in the subject in UGI
should be reused in case of a relogin.
Posted by "Xiao Kang (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-6687?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12854325#action_12854325 ]
Xiao Kang commented on HADOOP-6687:
-----------------------------------
Which revision is the patch against? Since no such method "public boolean commit() throws LoginException" found in http://svn.apache.org/repos/asf/hadoop/common/branches/branch-0.20/src/core/org/apache/hadoop/security/UserGroupInformation.java.
> user object in the subject in UGI should be reused in case of a relogin.
> -------------------------------------------------------------------------
>
> Key: HADOOP-6687
> URL: https://issues.apache.org/jira/browse/HADOOP-6687
> Project: Hadoop Common
> Issue Type: Bug
> Reporter: Jitendra Nath Pandey
> Attachments: HADOOP-6687-y20.2.patch
>
>
> In case of a relogin, a new user object is created in the subject. This causes the subject to lose some state for example authentication method. Instead, a new user object should not be added to the subject if one is already present.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (HADOOP-6687) user object in the subject in UGI
should be reused in case of a relogin.
Posted by "Boris Shkolnik (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-6687?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Boris Shkolnik updated HADOOP-6687:
-----------------------------------
Status: Resolved (was: Patch Available)
Hadoop Flags: [Reviewed]
Resolution: Fixed
+1
committed to trunk
> user object in the subject in UGI should be reused in case of a relogin.
> -------------------------------------------------------------------------
>
> Key: HADOOP-6687
> URL: https://issues.apache.org/jira/browse/HADOOP-6687
> Project: Hadoop Common
> Issue Type: Bug
> Reporter: Jitendra Nath Pandey
> Assignee: Jitendra Nath Pandey
> Attachments: HADOOP-6687-y20.2.patch, HADOOP-6687.2.patch, HADOOP-6687.3.patch
>
>
> In case of a relogin, a new user object is created in the subject. This causes the subject to lose some state for example authentication method. Instead, a new user object should not be added to the subject if one is already present.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (HADOOP-6687) user object in the subject in UGI
should be reused in case of a relogin.
Posted by "Jitendra Nath Pandey (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-6687?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jitendra Nath Pandey updated HADOOP-6687:
-----------------------------------------
Status: Patch Available (was: Open)
> user object in the subject in UGI should be reused in case of a relogin.
> -------------------------------------------------------------------------
>
> Key: HADOOP-6687
> URL: https://issues.apache.org/jira/browse/HADOOP-6687
> Project: Hadoop Common
> Issue Type: Bug
> Reporter: Jitendra Nath Pandey
> Assignee: Jitendra Nath Pandey
> Attachments: HADOOP-6687-y20.2.patch, HADOOP-6687.2.patch
>
>
> In case of a relogin, a new user object is created in the subject. This causes the subject to lose some state for example authentication method. Instead, a new user object should not be added to the subject if one is already present.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (HADOOP-6687) user object in the subject in UGI
should be reused in case of a relogin.
Posted by "Jitendra Nath Pandey (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-6687?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jitendra Nath Pandey updated HADOOP-6687:
-----------------------------------------
Attachment: HADOOP-6687-y20.2.patch
Patch for hadoop-20 added.
> user object in the subject in UGI should be reused in case of a relogin.
> -------------------------------------------------------------------------
>
> Key: HADOOP-6687
> URL: https://issues.apache.org/jira/browse/HADOOP-6687
> Project: Hadoop Common
> Issue Type: Bug
> Reporter: Jitendra Nath Pandey
> Attachments: HADOOP-6687-y20.2.patch
>
>
> In case of a relogin, a new user object is created in the subject. This causes the subject to lose some state for example authentication method. Instead, a new user object should not be added to the subject if one is already present.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (HADOOP-6687) user object in the subject in UGI
should be reused in case of a relogin.
Posted by "Jitendra Nath Pandey (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-6687?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jitendra Nath Pandey updated HADOOP-6687:
-----------------------------------------
Status: Patch Available (was: Open)
> user object in the subject in UGI should be reused in case of a relogin.
> -------------------------------------------------------------------------
>
> Key: HADOOP-6687
> URL: https://issues.apache.org/jira/browse/HADOOP-6687
> Project: Hadoop Common
> Issue Type: Bug
> Reporter: Jitendra Nath Pandey
> Assignee: Jitendra Nath Pandey
> Attachments: HADOOP-6687-y20.2.patch, HADOOP-6687.2.patch, HADOOP-6687.3.patch
>
>
> In case of a relogin, a new user object is created in the subject. This causes the subject to lose some state for example authentication method. Instead, a new user object should not be added to the subject if one is already present.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (HADOOP-6687) user object in the subject in UGI
should be reused in case of a relogin.
Posted by "Boris Shkolnik (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-6687?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12876438#action_12876438 ]
Boris Shkolnik commented on HADOOP-6687:
----------------------------------------
thanks Jitendra.
> user object in the subject in UGI should be reused in case of a relogin.
> -------------------------------------------------------------------------
>
> Key: HADOOP-6687
> URL: https://issues.apache.org/jira/browse/HADOOP-6687
> Project: Hadoop Common
> Issue Type: Bug
> Reporter: Jitendra Nath Pandey
> Assignee: Jitendra Nath Pandey
> Attachments: HADOOP-6687-y20.2.patch, HADOOP-6687.2.patch, HADOOP-6687.3.patch
>
>
> In case of a relogin, a new user object is created in the subject. This causes the subject to lose some state for example authentication method. Instead, a new user object should not be added to the subject if one is already present.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (HADOOP-6687) user object in the subject in UGI
should be reused in case of a relogin.
Posted by "Jitendra Nath Pandey (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-6687?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12855101#action_12855101 ]
Jitendra Nath Pandey commented on HADOOP-6687:
----------------------------------------------
The patch is against yahoo-hadoop-20, which has the security code. I should have clarified that.
It will be forward ported to trunk.
> user object in the subject in UGI should be reused in case of a relogin.
> -------------------------------------------------------------------------
>
> Key: HADOOP-6687
> URL: https://issues.apache.org/jira/browse/HADOOP-6687
> Project: Hadoop Common
> Issue Type: Bug
> Reporter: Jitendra Nath Pandey
> Attachments: HADOOP-6687-y20.2.patch
>
>
> In case of a relogin, a new user object is created in the subject. This causes the subject to lose some state for example authentication method. Instead, a new user object should not be added to the subject if one is already present.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (HADOOP-6687) user object in the subject in UGI
should be reused in case of a relogin.
Posted by "Hadoop QA (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-6687?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12875827#action_12875827 ]
Hadoop QA commented on HADOOP-6687:
-----------------------------------
+1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12446391/HADOOP-6687.2.patch
against trunk revision 951624.
+1 @author. The patch does not contain any @author tags.
+1 tests included. The patch appears to include 3 new or modified tests.
+1 javadoc. The javadoc tool did not generate any warning messages.
+1 javac. The applied patch does not increase the total number of javac compiler warnings.
+1 findbugs. The patch does not introduce any new Findbugs warnings.
+1 release audit. The applied patch does not increase the total number of release audit warnings.
+1 core tests. The patch passed core unit tests.
+1 contrib tests. The patch passed contrib unit tests.
Test results: http://hudson.zones.apache.org/hudson/job/Hadoop-Patch-h1.grid.sp2.yahoo.net/77/testReport/
Findbugs warnings: http://hudson.zones.apache.org/hudson/job/Hadoop-Patch-h1.grid.sp2.yahoo.net/77/artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
Checkstyle results: http://hudson.zones.apache.org/hudson/job/Hadoop-Patch-h1.grid.sp2.yahoo.net/77/artifact/trunk/build/test/checkstyle-errors.html
Console output: http://hudson.zones.apache.org/hudson/job/Hadoop-Patch-h1.grid.sp2.yahoo.net/77/console
This message is automatically generated.
> user object in the subject in UGI should be reused in case of a relogin.
> -------------------------------------------------------------------------
>
> Key: HADOOP-6687
> URL: https://issues.apache.org/jira/browse/HADOOP-6687
> Project: Hadoop Common
> Issue Type: Bug
> Reporter: Jitendra Nath Pandey
> Assignee: Jitendra Nath Pandey
> Attachments: HADOOP-6687-y20.2.patch, HADOOP-6687.2.patch
>
>
> In case of a relogin, a new user object is created in the subject. This causes the subject to lose some state for example authentication method. Instead, a new user object should not be added to the subject if one is already present.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (HADOOP-6687) user object in the subject in UGI
should be reused in case of a relogin.
Posted by "Jitendra Nath Pandey (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-6687?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jitendra Nath Pandey updated HADOOP-6687:
-----------------------------------------
Attachment: HADOOP-6687.2.patch
Patch for trunk.
> user object in the subject in UGI should be reused in case of a relogin.
> -------------------------------------------------------------------------
>
> Key: HADOOP-6687
> URL: https://issues.apache.org/jira/browse/HADOOP-6687
> Project: Hadoop Common
> Issue Type: Bug
> Reporter: Jitendra Nath Pandey
> Assignee: Jitendra Nath Pandey
> Attachments: HADOOP-6687-y20.2.patch, HADOOP-6687.2.patch
>
>
> In case of a relogin, a new user object is created in the subject. This causes the subject to lose some state for example authentication method. Instead, a new user object should not be added to the subject if one is already present.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Assigned: (HADOOP-6687) user object in the subject in UGI
should be reused in case of a relogin.
Posted by "Jitendra Nath Pandey (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-6687?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jitendra Nath Pandey reassigned HADOOP-6687:
--------------------------------------------
Assignee: Jitendra Nath Pandey
> user object in the subject in UGI should be reused in case of a relogin.
> -------------------------------------------------------------------------
>
> Key: HADOOP-6687
> URL: https://issues.apache.org/jira/browse/HADOOP-6687
> Project: Hadoop Common
> Issue Type: Bug
> Reporter: Jitendra Nath Pandey
> Assignee: Jitendra Nath Pandey
> Attachments: HADOOP-6687-y20.2.patch
>
>
> In case of a relogin, a new user object is created in the subject. This causes the subject to lose some state for example authentication method. Instead, a new user object should not be added to the subject if one is already present.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (HADOOP-6687) user object in the subject in UGI
should be reused in case of a relogin.
Posted by "Hudson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-6687?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12876632#action_12876632 ]
Hudson commented on HADOOP-6687:
--------------------------------
Integrated in Hadoop-Common-trunk #360 (See [http://hudson.zones.apache.org/hudson/job/Hadoop-Common-trunk/360/])
HADOOP-6687. user object in the subject in UGI should be reused in case of a relogin.
> user object in the subject in UGI should be reused in case of a relogin.
> -------------------------------------------------------------------------
>
> Key: HADOOP-6687
> URL: https://issues.apache.org/jira/browse/HADOOP-6687
> Project: Hadoop Common
> Issue Type: Bug
> Reporter: Jitendra Nath Pandey
> Assignee: Jitendra Nath Pandey
> Attachments: HADOOP-6687-y20.2.patch, HADOOP-6687.2.patch, HADOOP-6687.3.patch
>
>
> In case of a relogin, a new user object is created in the subject. This causes the subject to lose some state for example authentication method. Instead, a new user object should not be added to the subject if one is already present.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (HADOOP-6687) user object in the subject in UGI
should be reused in case of a relogin.
Posted by "Hudson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-6687?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12876455#action_12876455 ]
Hudson commented on HADOOP-6687:
--------------------------------
Integrated in Hadoop-Common-trunk-Commit #284 (See [http://hudson.zones.apache.org/hudson/job/Hadoop-Common-trunk-Commit/284/])
HADOOP-6687. user object in the subject in UGI should be reused in case of a relogin.
> user object in the subject in UGI should be reused in case of a relogin.
> -------------------------------------------------------------------------
>
> Key: HADOOP-6687
> URL: https://issues.apache.org/jira/browse/HADOOP-6687
> Project: Hadoop Common
> Issue Type: Bug
> Reporter: Jitendra Nath Pandey
> Assignee: Jitendra Nath Pandey
> Attachments: HADOOP-6687-y20.2.patch, HADOOP-6687.2.patch, HADOOP-6687.3.patch
>
>
> In case of a relogin, a new user object is created in the subject. This causes the subject to lose some state for example authentication method. Instead, a new user object should not be added to the subject if one is already present.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (HADOOP-6687) user object in the subject in UGI
should be reused in case of a relogin.
Posted by "Jitendra Nath Pandey (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-6687?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jitendra Nath Pandey updated HADOOP-6687:
-----------------------------------------
Attachment: HADOOP-6687.3.patch
> user object in the subject in UGI should be reused in case of a relogin.
> -------------------------------------------------------------------------
>
> Key: HADOOP-6687
> URL: https://issues.apache.org/jira/browse/HADOOP-6687
> Project: Hadoop Common
> Issue Type: Bug
> Reporter: Jitendra Nath Pandey
> Assignee: Jitendra Nath Pandey
> Attachments: HADOOP-6687-y20.2.patch, HADOOP-6687.2.patch, HADOOP-6687.3.patch
>
>
> In case of a relogin, a new user object is created in the subject. This causes the subject to lose some state for example authentication method. Instead, a new user object should not be added to the subject if one is already present.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (HADOOP-6687) user object in the subject in UGI
should be reused in case of a relogin.
Posted by "Hadoop QA (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-6687?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12876373#action_12876373 ]
Hadoop QA commented on HADOOP-6687:
-----------------------------------
+1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12446509/HADOOP-6687.3.patch
against trunk revision 951624.
+1 @author. The patch does not contain any @author tags.
+1 tests included. The patch appears to include 3 new or modified tests.
+1 javadoc. The javadoc tool did not generate any warning messages.
+1 javac. The applied patch does not increase the total number of javac compiler warnings.
+1 findbugs. The patch does not introduce any new Findbugs warnings.
+1 release audit. The applied patch does not increase the total number of release audit warnings.
+1 core tests. The patch passed core unit tests.
+1 contrib tests. The patch passed contrib unit tests.
Test results: http://hudson.zones.apache.org/hudson/job/Hadoop-Patch-h4.grid.sp2.yahoo.net/570/testReport/
Findbugs warnings: http://hudson.zones.apache.org/hudson/job/Hadoop-Patch-h4.grid.sp2.yahoo.net/570/artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
Checkstyle results: http://hudson.zones.apache.org/hudson/job/Hadoop-Patch-h4.grid.sp2.yahoo.net/570/artifact/trunk/build/test/checkstyle-errors.html
Console output: http://hudson.zones.apache.org/hudson/job/Hadoop-Patch-h4.grid.sp2.yahoo.net/570/console
This message is automatically generated.
> user object in the subject in UGI should be reused in case of a relogin.
> -------------------------------------------------------------------------
>
> Key: HADOOP-6687
> URL: https://issues.apache.org/jira/browse/HADOOP-6687
> Project: Hadoop Common
> Issue Type: Bug
> Reporter: Jitendra Nath Pandey
> Assignee: Jitendra Nath Pandey
> Attachments: HADOOP-6687-y20.2.patch, HADOOP-6687.2.patch, HADOOP-6687.3.patch
>
>
> In case of a relogin, a new user object is created in the subject. This causes the subject to lose some state for example authentication method. Instead, a new user object should not be added to the subject if one is already present.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (HADOOP-6687) user object in the subject in UGI
should be reused in case of a relogin.
Posted by "Jitendra Nath Pandey (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-6687?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jitendra Nath Pandey updated HADOOP-6687:
-----------------------------------------
Status: Open (was: Patch Available)
> user object in the subject in UGI should be reused in case of a relogin.
> -------------------------------------------------------------------------
>
> Key: HADOOP-6687
> URL: https://issues.apache.org/jira/browse/HADOOP-6687
> Project: Hadoop Common
> Issue Type: Bug
> Reporter: Jitendra Nath Pandey
> Assignee: Jitendra Nath Pandey
> Attachments: HADOOP-6687-y20.2.patch, HADOOP-6687.2.patch, HADOOP-6687.3.patch
>
>
> In case of a relogin, a new user object is created in the subject. This causes the subject to lose some state for example authentication method. Instead, a new user object should not be added to the subject if one is already present.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.