[
https://issues.apache.org/jira/browse/HADOOP-8932?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13480873#comment-13480873
]
Hudson commented on HADOOP-8932:
--------------------------------
Integrated in Hadoop-trunk-Commit #2903 (See
[https://builds.apache.org/job/Hadoop-trunk-Commit/2903/])
Change incorrect jira number HADOOP-8923 to HADOOP-8932 introduced in
commit r1398883. (Revision 1400552)
Result = SUCCESS
suresh : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1400552
Files :
* /hadoop/common/trunk/hadoop-common-project/hadoop-common/CHANGES.txt
> JNI-based user-group mapping modules can be too chatty on lookup failures
> -------------------------------------------------------------------------
>
> Key: HADOOP-8932
> URL: https://issues.apache.org/jira/browse/HADOOP-8932
> Project: Hadoop Common
> Issue Type: Improvement
> Components: security
> Affects Versions: 3.0.0, 2.0.3-alpha, 0.23.5
> Reporter: Kihwal Lee
> Assignee: Kihwal Lee
> Fix For: 3.0.0, 2.0.3-alpha, 0.23.5
>
> Attachments: hadoop-8932.patch.txt
>
>
> On a user/group lookup failure, JniBasedUnixGroupsMapping and
> JniBasedUnixGroupsNetgroupMapping are logging the
> full stack trace at WARN level. Since the caller of these methods is already
> logging errors, this is not needed. In branch-1, just one line is logged, so
> we don't need this change there.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
