[
https://issues.apache.org/jira/browse/HADOOP-8611?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13438222#comment-13438222
]
Hadoop QA commented on HADOOP-8611:
-----------------------------------
+1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12541645/HADOOP-8611.patch
against trunk revision .
+1 @author. The patch does not contain any @author tags.
+1 tests included. The patch appears to include 1 new or modified test
files.
+1 javac. The applied patch does not increase the total number of javac
compiler warnings.
+1 javadoc. The javadoc tool did not generate any warning messages.
+1 eclipse:eclipse. The patch built with eclipse:eclipse.
+1 findbugs. The patch does not introduce any new Findbugs (version 1.3.9)
warnings.
+1 release audit. The applied patch does not increase the total number of
release audit warnings.
+1 core tests. The patch passed unit tests in
hadoop-common-project/hadoop-common.
+1 contrib tests. The patch passed contrib unit tests.
Test results:
https://builds.apache.org/job/PreCommit-HADOOP-Build/1330//testReport/
Console output:
https://builds.apache.org/job/PreCommit-HADOOP-Build/1330//console
This message is automatically generated.
> Allow fall-back to the shell-based implementation when JNI-based users-group
> mapping fails
> ------------------------------------------------------------------------------------------
>
> Key: HADOOP-8611
> URL: https://issues.apache.org/jira/browse/HADOOP-8611
> Project: Hadoop Common
> Issue Type: Bug
> Components: security
> Affects Versions: 1.0.3, 0.23.0, 2.0.0-alpha
> Reporter: Kihwal Lee
> Assignee: Robert Parker
> Fix For: 1.2.0, 0.23.3, 2.1.0-alpha, 3.0.0, 2.2.0-alpha
>
> Attachments: HADOOP-8611-branch1.patch, HADOOP-8611-branch1.patch,
> HADOOP-8611.patch, HADOOP-8611.patch, HADOOP-8611.patch
>
>
> When the JNI-based users-group mapping is enabled, the process/command will
> fail if the native library, libhadoop.so, cannot be found. This mostly
> happens at client-side where users may use hadoop programatically. Instead of
> failing, falling back to the shell-based implementation will be desirable.
> Depending on how cluster is configured, use of the native netgroup mapping
> cannot be subsituted by the shell-based default. For this reason, this
> behavior must be configurable with the default being "disabled".
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
