[jira] [Commented] (HBASE-9221) Provide interface for getting a User in the client
[ https://issues.apache.org/jira/browse/HBASE-9221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13810753#comment-13810753 ] Hudson commented on HBASE-9221: --- SUCCESS: Integrated in HBase-0.94-security #326 (See [https://builds.apache.org/job/HBase-0.94-security/326/]) HBASE-9221: Provide interface for getting a User in the client (jyates: rev 1536930) * /hbase/branches/0.94/security/src/main/java/org/apache/hadoop/hbase/ipc/SecureClient.java * /hbase/branches/0.94/security/src/main/java/org/apache/hadoop/hbase/ipc/SecureConnectionHeader.java * /hbase/branches/0.94/security/src/main/java/org/apache/hadoop/hbase/ipc/SecureRpcEngine.java * /hbase/branches/0.94/security/src/main/java/org/apache/hadoop/hbase/ipc/SecureServer.java * /hbase/branches/0.94/security/src/main/java/org/apache/hadoop/hbase/security/access/AccessController.java * /hbase/branches/0.94/security/src/main/java/org/apache/hadoop/hbase/security/access/SecureBulkLoadEndpoint.java * /hbase/branches/0.94/security/src/main/java/org/apache/hadoop/hbase/security/access/TableAuthManager.java * /hbase/branches/0.94/security/src/test/java/org/apache/hadoop/hbase/mapreduce/TestSecureLoadIncrementalHFiles.java * /hbase/branches/0.94/security/src/test/java/org/apache/hadoop/hbase/mapreduce/TestSecureLoadIncrementalHFilesSplitRecovery.java * /hbase/branches/0.94/src/main/java/org/apache/hadoop/hbase/client/HConnectionManager.java * /hbase/branches/0.94/src/main/java/org/apache/hadoop/hbase/client/UserProvider.java * /hbase/branches/0.94/src/main/java/org/apache/hadoop/hbase/ipc/WritableRpcEngine.java * /hbase/branches/0.94/src/main/java/org/apache/hadoop/hbase/mapred/TableMapReduceUtil.java * /hbase/branches/0.94/src/main/java/org/apache/hadoop/hbase/mapreduce/LoadIncrementalHFiles.java * /hbase/branches/0.94/src/main/java/org/apache/hadoop/hbase/mapreduce/TableMapReduceUtil.java * /hbase/branches/0.94/src/main/java/org/apache/hadoop/hbase/master/HMaster.java * /hbase/branches/0.94/src/main/java/org/apache/hadoop/hbase/regionserver/HRegionServer.java * /hbase/branches/0.94/src/main/java/org/apache/hadoop/hbase/rest/Main.java * /hbase/branches/0.94/src/main/java/org/apache/hadoop/hbase/security/User.java * /hbase/branches/0.94/src/main/java/org/apache/hadoop/hbase/thrift/ThriftServer.java * /hbase/branches/0.94/src/main/java/org/apache/hadoop/hbase/util/HBaseFsck.java * /hbase/branches/0.94/src/test/java/org/apache/hadoop/hbase/mapreduce/HadoopSecurityEnabledUserProviderForTesting.java * /hbase/branches/0.94/src/test/java/org/apache/hadoop/hbase/mapreduce/TestLoadIncrementalHFiles.java * /hbase/branches/0.94/src/test/java/org/apache/hadoop/hbase/mapreduce/TestLoadIncrementalHFilesSplitRecovery.java * /hbase/branches/0.94/src/test/java/org/apache/hadoop/hbase/master/TestMasterStatusServlet.java Provide interface for getting a User in the client -- Key: HBASE-9221 URL: https://issues.apache.org/jira/browse/HBASE-9221 Project: HBase Issue Type: Improvement Components: Client, hadoop2, security Affects Versions: 0.98.0, 0.95.2, 0.94.12 Reporter: Jesse Yates Assignee: Jesse Yates Fix For: 0.98.0, 0.94.13, 0.96.1 Attachments: hbase-9221-0.94-v0.patch, hbase-9221-0.94-v1.patch, hbase-9221-0.94-v3.patch, hbase-9221-0.94-v4.patch, hbase-9221-0.96-trunk.addendum, hbase-9221-0.96-v0.patch, hbase-9221-0.96-v1.patch, hbase-9221-trunk-v0.patch, hbase-9221-trunk-v1.patch, hbase-9221-trunk-v2.patch, hbase-9221-trunk-v3.patch, hbase-9221-trunk-v4.patch, hbase-9221-trunk-v5.patch Sometimes, users will want to provide their own User class depending on the type of security they will support in their local environment. For instance, running Hadoop1 vs Hadoop2 vs CDH means potentially different ways of getting the UserGroupInformation. This issue abstracts out the mechanism by which we obtain an o.a.h.hbase.security.User to a UserProvider. This UserProvider can then be extented as a Hadoop 1/2 shim as well as supporting custom authentication code. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (HBASE-9221) Provide interface for getting a User in the client
[ https://issues.apache.org/jira/browse/HBASE-9221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13809066#comment-13809066 ] Hudson commented on HBASE-9221: --- SUCCESS: Integrated in HBase-TRUNK-on-Hadoop-2.0.0 #817 (See [https://builds.apache.org/job/HBase-TRUNK-on-Hadoop-2.0.0/817/]) HBASE-9221: Provide interface for getting a User in the client: ADDENDUM (jyates: rev 1536944) * /hbase/trunk/hbase-client/pom.xml * /hbase/trunk/hbase-common/src/main/java/org/apache/hadoop/hbase/security/UserProvider.java HBASE-9221: Provide interface for getting a User in the client (jyates: rev 1536937) * /hbase/trunk/hbase-client/pom.xml * /hbase/trunk/hbase-client/src/main/java/org/apache/hadoop/hbase/client/HConnectionKey.java * /hbase/trunk/hbase-client/src/main/java/org/apache/hadoop/hbase/client/HConnectionManager.java * /hbase/trunk/hbase-client/src/main/java/org/apache/hadoop/hbase/ipc/RpcClient.java * /hbase/trunk/hbase-client/src/main/java/org/apache/hadoop/hbase/security/User.java * /hbase/trunk/hbase-common/pom.xml * /hbase/trunk/hbase-common/src/main/java/org/apache/hadoop/hbase/BaseConfigurable.java * /hbase/trunk/hbase-common/src/main/java/org/apache/hadoop/hbase/security * /hbase/trunk/hbase-common/src/main/java/org/apache/hadoop/hbase/security/User.java * /hbase/trunk/hbase-common/src/main/java/org/apache/hadoop/hbase/security/UserProvider.java * /hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/BaseConfigurable.java * /hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/ipc/CallRunner.java * /hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/ipc/RpcServer.java * /hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/mapred/TableMapReduceUtil.java * /hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/mapreduce/LoadIncrementalHFiles.java * /hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/mapreduce/TableMapReduceUtil.java * /hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/master/HMaster.java * /hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/HRegionServer.java * /hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/rest/RESTServer.java * /hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/rest/RESTServlet.java * /hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/security/access/AccessController.java * /hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/security/access/SecureBulkLoadEndpoint.java * /hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/security/access/TableAuthManager.java * /hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/util/HBaseFsck.java * /hbase/trunk/hbase-server/src/test/java/org/apache/hadoop/hbase/ipc/TestCallRunner.java * /hbase/trunk/hbase-server/src/test/java/org/apache/hadoop/hbase/mapreduce/HadoopSecurityEnabledUserProviderForTesting.java * /hbase/trunk/hbase-server/src/test/java/org/apache/hadoop/hbase/mapreduce/TestLoadIncrementalHFiles.java * /hbase/trunk/hbase-server/src/test/java/org/apache/hadoop/hbase/mapreduce/TestLoadIncrementalHFilesSplitRecovery.java * /hbase/trunk/hbase-server/src/test/java/org/apache/hadoop/hbase/mapreduce/TestSecureLoadIncrementalHFiles.java * /hbase/trunk/hbase-server/src/test/java/org/apache/hadoop/hbase/mapreduce/TestSecureLoadIncrementalHFilesSplitRecovery.java * /hbase/trunk/hbase-thrift/src/main/java/org/apache/hadoop/hbase/thrift/ThriftServer.java Provide interface for getting a User in the client -- Key: HBASE-9221 URL: https://issues.apache.org/jira/browse/HBASE-9221 Project: HBase Issue Type: Improvement Components: Client, hadoop2, security Affects Versions: 0.98.0, 0.95.2, 0.94.12 Reporter: Jesse Yates Assignee: Jesse Yates Fix For: 0.98.0, 0.94.13, 0.96.1 Attachments: hbase-9221-0.94-v0.patch, hbase-9221-0.94-v1.patch, hbase-9221-0.94-v3.patch, hbase-9221-0.94-v4.patch, hbase-9221-0.96-trunk.addendum, hbase-9221-0.96-v0.patch, hbase-9221-0.96-v1.patch, hbase-9221-trunk-v0.patch, hbase-9221-trunk-v1.patch, hbase-9221-trunk-v2.patch, hbase-9221-trunk-v3.patch, hbase-9221-trunk-v4.patch, hbase-9221-trunk-v5.patch Sometimes, users will want to provide their own User class depending on the type of security they will support in their local environment. For instance, running Hadoop1 vs Hadoop2 vs CDH means potentially different ways of getting the UserGroupInformation. This issue abstracts out the mechanism by which we obtain an o.a.h.hbase.security.User to a UserProvider. This UserProvider can then be extented as a Hadoop 1/2 shim as well as supporting custom authentication code. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (HBASE-9221) Provide interface for getting a User in the client
[ https://issues.apache.org/jira/browse/HBASE-9221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13808263#comment-13808263 ] Jesse Yates commented on HBASE-9221: Found the issues. (1) AccessController was just modified wrong - did instantiation at the wrong spot, (2) is HBaseSecurityEnabled is apparently used for determining Kerberos-based authentication - didn't realize full implication there. Fixed patches coming shortly Provide interface for getting a User in the client -- Key: HBASE-9221 URL: https://issues.apache.org/jira/browse/HBASE-9221 Project: HBase Issue Type: Improvement Components: Client, hadoop2, security Affects Versions: 0.98.0, 0.95.2, 0.94.12 Reporter: Jesse Yates Assignee: Jesse Yates Fix For: 0.98.0, 0.94.13, 0.96.1 Attachments: hbase-9221-0.94-v0.patch, hbase-9221-0.94-v1.patch, hbase-9221-0.94-v3.patch, hbase-9221-0.96-v0.patch, hbase-9221-trunk-v0.patch, hbase-9221-trunk-v1.patch, hbase-9221-trunk-v2.patch, hbase-9221-trunk-v3.patch, hbase-9221-trunk-v4.patch Sometimes, users will want to provide their own User class depending on the type of security they will support in their local environment. For instance, running Hadoop1 vs Hadoop2 vs CDH means potentially different ways of getting the UserGroupInformation. This issue abstracts out the mechanism by which we obtain an o.a.h.hbase.security.User to a UserProvider. This UserProvider can then be extented as a Hadoop 1/2 shim as well as supporting custom authentication code. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (HBASE-9221) Provide interface for getting a User in the client
[ https://issues.apache.org/jira/browse/HBASE-9221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13808435#comment-13808435 ] Lars Hofhansl commented on HBASE-9221: -- +1 Provide interface for getting a User in the client -- Key: HBASE-9221 URL: https://issues.apache.org/jira/browse/HBASE-9221 Project: HBase Issue Type: Improvement Components: Client, hadoop2, security Affects Versions: 0.98.0, 0.95.2, 0.94.12 Reporter: Jesse Yates Assignee: Jesse Yates Fix For: 0.98.0, 0.94.13, 0.96.1 Attachments: hbase-9221-0.94-v0.patch, hbase-9221-0.94-v1.patch, hbase-9221-0.94-v3.patch, hbase-9221-0.94-v4.patch, hbase-9221-0.96-v0.patch, hbase-9221-0.96-v1.patch, hbase-9221-trunk-v0.patch, hbase-9221-trunk-v1.patch, hbase-9221-trunk-v2.patch, hbase-9221-trunk-v3.patch, hbase-9221-trunk-v4.patch, hbase-9221-trunk-v5.patch Sometimes, users will want to provide their own User class depending on the type of security they will support in their local environment. For instance, running Hadoop1 vs Hadoop2 vs CDH means potentially different ways of getting the UserGroupInformation. This issue abstracts out the mechanism by which we obtain an o.a.h.hbase.security.User to a UserProvider. This UserProvider can then be extented as a Hadoop 1/2 shim as well as supporting custom authentication code. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (HBASE-9221) Provide interface for getting a User in the client
[
https://issues.apache.org/jira/browse/HBASE-9221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13808535#comment-13808535
]
Hadoop QA commented on HBASE-9221:
--
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12610920/hbase-9221-trunk-v5.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 17 new
or modified tests.
{color:green}+1 hadoop1.0{color}. The patch compiles against the hadoop
1.0 profile.
{color:green}+1 hadoop2.0{color}. The patch compiles against the hadoop
2.0 profile.
{color:red}-1 javadoc{color}. The javadoc tool appears to have generated 1
warning messages.
{color:red}-1 javac{color}. The applied patch generated 12 javac compiler
warnings (more than the trunk's current 4 warnings).
{color:red}-1 findbugs{color}. The patch appears to introduce 1 new
Findbugs (version 1.3.9) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 lineLengths{color}. The patch does not introduce lines
longer than 100
{color:red}-1 site{color}. The patch appears to cause mvn site goal to
fail.
{color:green}+1 core tests{color}. The patch passed unit tests in .
Test results:
https://builds.apache.org/job/PreCommit-HBASE-Build/7668//testReport/
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/7668//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-prefix-tree.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/7668//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-client.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/7668//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-common.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/7668//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-protocol.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/7668//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-server.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/7668//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop1-compat.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/7668//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-examples.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/7668//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-thrift.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/7668//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop-compat.html
Console output:
https://builds.apache.org/job/PreCommit-HBASE-Build/7668//console
This message is automatically generated.
Provide interface for getting a User in the client
--
Key: HBASE-9221
URL: https://issues.apache.org/jira/browse/HBASE-9221
Project: HBase
Issue Type: Improvement
Components: Client, hadoop2, security
Affects Versions: 0.98.0, 0.95.2, 0.94.12
Reporter: Jesse Yates
Assignee: Jesse Yates
Fix For: 0.98.0, 0.94.13, 0.96.1
Attachments: hbase-9221-0.94-v0.patch, hbase-9221-0.94-v1.patch,
hbase-9221-0.94-v3.patch, hbase-9221-0.94-v4.patch, hbase-9221-0.96-v0.patch,
hbase-9221-0.96-v1.patch, hbase-9221-trunk-v0.patch,
hbase-9221-trunk-v1.patch, hbase-9221-trunk-v2.patch,
hbase-9221-trunk-v3.patch, hbase-9221-trunk-v4.patch,
hbase-9221-trunk-v5.patch
Sometimes, users will want to provide their own User class depending on the
type of security they will support in their local environment. For instance,
running Hadoop1 vs Hadoop2 vs CDH means potentially different ways of getting
the UserGroupInformation.
This issue abstracts out the mechanism by which we obtain an
o.a.h.hbase.security.User to a UserProvider. This UserProvider can then be
extented as a Hadoop 1/2 shim as well as supporting custom authentication
code.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
[jira] [Commented] (HBASE-9221) Provide interface for getting a User in the client
[ https://issues.apache.org/jira/browse/HBASE-9221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13808677#comment-13808677 ] Hudson commented on HBASE-9221: --- FAILURE: Integrated in HBase-0.94 #1189 (See [https://builds.apache.org/job/HBase-0.94/1189/]) HBASE-9221: Provide interface for getting a User in the client (jyates: rev 1536930) * /hbase/branches/0.94/security/src/main/java/org/apache/hadoop/hbase/ipc/SecureClient.java * /hbase/branches/0.94/security/src/main/java/org/apache/hadoop/hbase/ipc/SecureConnectionHeader.java * /hbase/branches/0.94/security/src/main/java/org/apache/hadoop/hbase/ipc/SecureRpcEngine.java * /hbase/branches/0.94/security/src/main/java/org/apache/hadoop/hbase/ipc/SecureServer.java * /hbase/branches/0.94/security/src/main/java/org/apache/hadoop/hbase/security/access/AccessController.java * /hbase/branches/0.94/security/src/main/java/org/apache/hadoop/hbase/security/access/SecureBulkLoadEndpoint.java * /hbase/branches/0.94/security/src/main/java/org/apache/hadoop/hbase/security/access/TableAuthManager.java * /hbase/branches/0.94/security/src/test/java/org/apache/hadoop/hbase/mapreduce/TestSecureLoadIncrementalHFiles.java * /hbase/branches/0.94/security/src/test/java/org/apache/hadoop/hbase/mapreduce/TestSecureLoadIncrementalHFilesSplitRecovery.java * /hbase/branches/0.94/src/main/java/org/apache/hadoop/hbase/client/HConnectionManager.java * /hbase/branches/0.94/src/main/java/org/apache/hadoop/hbase/client/UserProvider.java * /hbase/branches/0.94/src/main/java/org/apache/hadoop/hbase/ipc/WritableRpcEngine.java * /hbase/branches/0.94/src/main/java/org/apache/hadoop/hbase/mapred/TableMapReduceUtil.java * /hbase/branches/0.94/src/main/java/org/apache/hadoop/hbase/mapreduce/LoadIncrementalHFiles.java * /hbase/branches/0.94/src/main/java/org/apache/hadoop/hbase/mapreduce/TableMapReduceUtil.java * /hbase/branches/0.94/src/main/java/org/apache/hadoop/hbase/master/HMaster.java * /hbase/branches/0.94/src/main/java/org/apache/hadoop/hbase/regionserver/HRegionServer.java * /hbase/branches/0.94/src/main/java/org/apache/hadoop/hbase/rest/Main.java * /hbase/branches/0.94/src/main/java/org/apache/hadoop/hbase/security/User.java * /hbase/branches/0.94/src/main/java/org/apache/hadoop/hbase/thrift/ThriftServer.java * /hbase/branches/0.94/src/main/java/org/apache/hadoop/hbase/util/HBaseFsck.java * /hbase/branches/0.94/src/test/java/org/apache/hadoop/hbase/mapreduce/HadoopSecurityEnabledUserProviderForTesting.java * /hbase/branches/0.94/src/test/java/org/apache/hadoop/hbase/mapreduce/TestLoadIncrementalHFiles.java * /hbase/branches/0.94/src/test/java/org/apache/hadoop/hbase/mapreduce/TestLoadIncrementalHFilesSplitRecovery.java * /hbase/branches/0.94/src/test/java/org/apache/hadoop/hbase/master/TestMasterStatusServlet.java Provide interface for getting a User in the client -- Key: HBASE-9221 URL: https://issues.apache.org/jira/browse/HBASE-9221 Project: HBase Issue Type: Improvement Components: Client, hadoop2, security Affects Versions: 0.98.0, 0.95.2, 0.94.12 Reporter: Jesse Yates Assignee: Jesse Yates Fix For: 0.98.0, 0.94.13, 0.96.1 Attachments: hbase-9221-0.94-v0.patch, hbase-9221-0.94-v1.patch, hbase-9221-0.94-v3.patch, hbase-9221-0.94-v4.patch, hbase-9221-0.96-trunk.addendum, hbase-9221-0.96-v0.patch, hbase-9221-0.96-v1.patch, hbase-9221-trunk-v0.patch, hbase-9221-trunk-v1.patch, hbase-9221-trunk-v2.patch, hbase-9221-trunk-v3.patch, hbase-9221-trunk-v4.patch, hbase-9221-trunk-v5.patch Sometimes, users will want to provide their own User class depending on the type of security they will support in their local environment. For instance, running Hadoop1 vs Hadoop2 vs CDH means potentially different ways of getting the UserGroupInformation. This issue abstracts out the mechanism by which we obtain an o.a.h.hbase.security.User to a UserProvider. This UserProvider can then be extented as a Hadoop 1/2 shim as well as supporting custom authentication code. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (HBASE-9221) Provide interface for getting a User in the client
[ https://issues.apache.org/jira/browse/HBASE-9221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13808732#comment-13808732 ] Hudson commented on HBASE-9221: --- SUCCESS: Integrated in hbase-0.96 #169 (See [https://builds.apache.org/job/hbase-0.96/169/]) HBASE-9221: Provide interface for getting a User in the client: ADDENDUM (jyates: rev 1536945) * /hbase/branches/0.96/hbase-client/pom.xml * /hbase/branches/0.96/hbase-common/src/main/java/org/apache/hadoop/hbase/security/UserProvider.java HBASE-9221: Provide interface for getting a User in the client (jyates: rev 1536936) * /hbase/branches/0.96/hbase-client/pom.xml * /hbase/branches/0.96/hbase-client/src/main/java/org/apache/hadoop/hbase/client/HConnectionKey.java * /hbase/branches/0.96/hbase-client/src/main/java/org/apache/hadoop/hbase/client/HConnectionManager.java * /hbase/branches/0.96/hbase-client/src/main/java/org/apache/hadoop/hbase/ipc/RpcClient.java * /hbase/branches/0.96/hbase-client/src/main/java/org/apache/hadoop/hbase/security/User.java * /hbase/branches/0.96/hbase-common/pom.xml * /hbase/branches/0.96/hbase-common/src/main/java/org/apache/hadoop/hbase/BaseConfigurable.java * /hbase/branches/0.96/hbase-common/src/main/java/org/apache/hadoop/hbase/security * /hbase/branches/0.96/hbase-common/src/main/java/org/apache/hadoop/hbase/security/User.java * /hbase/branches/0.96/hbase-common/src/main/java/org/apache/hadoop/hbase/security/UserProvider.java * /hbase/branches/0.96/hbase-server/src/main/java/org/apache/hadoop/hbase/BaseConfigurable.java * /hbase/branches/0.96/hbase-server/src/main/java/org/apache/hadoop/hbase/ipc/RpcServer.java * /hbase/branches/0.96/hbase-server/src/main/java/org/apache/hadoop/hbase/mapred/TableMapReduceUtil.java * /hbase/branches/0.96/hbase-server/src/main/java/org/apache/hadoop/hbase/mapreduce/LoadIncrementalHFiles.java * /hbase/branches/0.96/hbase-server/src/main/java/org/apache/hadoop/hbase/mapreduce/TableMapReduceUtil.java * /hbase/branches/0.96/hbase-server/src/main/java/org/apache/hadoop/hbase/master/HMaster.java * /hbase/branches/0.96/hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/HRegionServer.java * /hbase/branches/0.96/hbase-server/src/main/java/org/apache/hadoop/hbase/rest/RESTServer.java * /hbase/branches/0.96/hbase-server/src/main/java/org/apache/hadoop/hbase/rest/RESTServlet.java * /hbase/branches/0.96/hbase-server/src/main/java/org/apache/hadoop/hbase/security/access/AccessController.java * /hbase/branches/0.96/hbase-server/src/main/java/org/apache/hadoop/hbase/security/access/SecureBulkLoadEndpoint.java * /hbase/branches/0.96/hbase-server/src/main/java/org/apache/hadoop/hbase/security/access/TableAuthManager.java * /hbase/branches/0.96/hbase-server/src/main/java/org/apache/hadoop/hbase/util/HBaseFsck.java * /hbase/branches/0.96/hbase-server/src/test/java/org/apache/hadoop/hbase/mapreduce/HadoopSecurityEnabledUserProviderForTesting.java * /hbase/branches/0.96/hbase-server/src/test/java/org/apache/hadoop/hbase/mapreduce/TestLoadIncrementalHFiles.java * /hbase/branches/0.96/hbase-server/src/test/java/org/apache/hadoop/hbase/mapreduce/TestLoadIncrementalHFilesSplitRecovery.java * /hbase/branches/0.96/hbase-server/src/test/java/org/apache/hadoop/hbase/mapreduce/TestSecureLoadIncrementalHFiles.java * /hbase/branches/0.96/hbase-server/src/test/java/org/apache/hadoop/hbase/mapreduce/TestSecureLoadIncrementalHFilesSplitRecovery.java * /hbase/branches/0.96/hbase-thrift/src/main/java/org/apache/hadoop/hbase/thrift/ThriftServer.java Provide interface for getting a User in the client -- Key: HBASE-9221 URL: https://issues.apache.org/jira/browse/HBASE-9221 Project: HBase Issue Type: Improvement Components: Client, hadoop2, security Affects Versions: 0.98.0, 0.95.2, 0.94.12 Reporter: Jesse Yates Assignee: Jesse Yates Fix For: 0.98.0, 0.94.13, 0.96.1 Attachments: hbase-9221-0.94-v0.patch, hbase-9221-0.94-v1.patch, hbase-9221-0.94-v3.patch, hbase-9221-0.94-v4.patch, hbase-9221-0.96-trunk.addendum, hbase-9221-0.96-v0.patch, hbase-9221-0.96-v1.patch, hbase-9221-trunk-v0.patch, hbase-9221-trunk-v1.patch, hbase-9221-trunk-v2.patch, hbase-9221-trunk-v3.patch, hbase-9221-trunk-v4.patch, hbase-9221-trunk-v5.patch Sometimes, users will want to provide their own User class depending on the type of security they will support in their local environment. For instance, running Hadoop1 vs Hadoop2 vs CDH means potentially different ways of getting the UserGroupInformation. This issue abstracts out the mechanism by which we obtain an o.a.h.hbase.security.User to a UserProvider. This UserProvider can then be extented as a Hadoop 1/2 shim as well as supporting custom authentication code. -- This message was sent by
[jira] [Commented] (HBASE-9221) Provide interface for getting a User in the client
[ https://issues.apache.org/jira/browse/HBASE-9221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13808744#comment-13808744 ] Hudson commented on HBASE-9221: --- SUCCESS: Integrated in HBase-TRUNK #4655 (See [https://builds.apache.org/job/HBase-TRUNK/4655/]) HBASE-9221: Provide interface for getting a User in the client: ADDENDUM (jyates: rev 1536944) * /hbase/trunk/hbase-client/pom.xml * /hbase/trunk/hbase-common/src/main/java/org/apache/hadoop/hbase/security/UserProvider.java HBASE-9221: Provide interface for getting a User in the client (jyates: rev 1536937) * /hbase/trunk/hbase-client/pom.xml * /hbase/trunk/hbase-client/src/main/java/org/apache/hadoop/hbase/client/HConnectionKey.java * /hbase/trunk/hbase-client/src/main/java/org/apache/hadoop/hbase/client/HConnectionManager.java * /hbase/trunk/hbase-client/src/main/java/org/apache/hadoop/hbase/ipc/RpcClient.java * /hbase/trunk/hbase-client/src/main/java/org/apache/hadoop/hbase/security/User.java * /hbase/trunk/hbase-common/pom.xml * /hbase/trunk/hbase-common/src/main/java/org/apache/hadoop/hbase/BaseConfigurable.java * /hbase/trunk/hbase-common/src/main/java/org/apache/hadoop/hbase/security * /hbase/trunk/hbase-common/src/main/java/org/apache/hadoop/hbase/security/User.java * /hbase/trunk/hbase-common/src/main/java/org/apache/hadoop/hbase/security/UserProvider.java * /hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/BaseConfigurable.java * /hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/ipc/CallRunner.java * /hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/ipc/RpcServer.java * /hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/mapred/TableMapReduceUtil.java * /hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/mapreduce/LoadIncrementalHFiles.java * /hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/mapreduce/TableMapReduceUtil.java * /hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/master/HMaster.java * /hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/HRegionServer.java * /hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/rest/RESTServer.java * /hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/rest/RESTServlet.java * /hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/security/access/AccessController.java * /hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/security/access/SecureBulkLoadEndpoint.java * /hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/security/access/TableAuthManager.java * /hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/util/HBaseFsck.java * /hbase/trunk/hbase-server/src/test/java/org/apache/hadoop/hbase/ipc/TestCallRunner.java * /hbase/trunk/hbase-server/src/test/java/org/apache/hadoop/hbase/mapreduce/HadoopSecurityEnabledUserProviderForTesting.java * /hbase/trunk/hbase-server/src/test/java/org/apache/hadoop/hbase/mapreduce/TestLoadIncrementalHFiles.java * /hbase/trunk/hbase-server/src/test/java/org/apache/hadoop/hbase/mapreduce/TestLoadIncrementalHFilesSplitRecovery.java * /hbase/trunk/hbase-server/src/test/java/org/apache/hadoop/hbase/mapreduce/TestSecureLoadIncrementalHFiles.java * /hbase/trunk/hbase-server/src/test/java/org/apache/hadoop/hbase/mapreduce/TestSecureLoadIncrementalHFilesSplitRecovery.java * /hbase/trunk/hbase-thrift/src/main/java/org/apache/hadoop/hbase/thrift/ThriftServer.java Provide interface for getting a User in the client -- Key: HBASE-9221 URL: https://issues.apache.org/jira/browse/HBASE-9221 Project: HBase Issue Type: Improvement Components: Client, hadoop2, security Affects Versions: 0.98.0, 0.95.2, 0.94.12 Reporter: Jesse Yates Assignee: Jesse Yates Fix For: 0.98.0, 0.94.13, 0.96.1 Attachments: hbase-9221-0.94-v0.patch, hbase-9221-0.94-v1.patch, hbase-9221-0.94-v3.patch, hbase-9221-0.94-v4.patch, hbase-9221-0.96-trunk.addendum, hbase-9221-0.96-v0.patch, hbase-9221-0.96-v1.patch, hbase-9221-trunk-v0.patch, hbase-9221-trunk-v1.patch, hbase-9221-trunk-v2.patch, hbase-9221-trunk-v3.patch, hbase-9221-trunk-v4.patch, hbase-9221-trunk-v5.patch Sometimes, users will want to provide their own User class depending on the type of security they will support in their local environment. For instance, running Hadoop1 vs Hadoop2 vs CDH means potentially different ways of getting the UserGroupInformation. This issue abstracts out the mechanism by which we obtain an o.a.h.hbase.security.User to a UserProvider. This UserProvider can then be extented as a Hadoop 1/2 shim as well as supporting custom authentication code. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (HBASE-9221) Provide interface for getting a User in the client
[ https://issues.apache.org/jira/browse/HBASE-9221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13808777#comment-13808777 ] Hudson commented on HBASE-9221: --- FAILURE: Integrated in hbase-0.96-hadoop2 #106 (See [https://builds.apache.org/job/hbase-0.96-hadoop2/106/]) HBASE-9221: Provide interface for getting a User in the client: ADDENDUM (jyates: rev 1536945) * /hbase/branches/0.96/hbase-client/pom.xml * /hbase/branches/0.96/hbase-common/src/main/java/org/apache/hadoop/hbase/security/UserProvider.java HBASE-9221: Provide interface for getting a User in the client (jyates: rev 1536936) * /hbase/branches/0.96/hbase-client/pom.xml * /hbase/branches/0.96/hbase-client/src/main/java/org/apache/hadoop/hbase/client/HConnectionKey.java * /hbase/branches/0.96/hbase-client/src/main/java/org/apache/hadoop/hbase/client/HConnectionManager.java * /hbase/branches/0.96/hbase-client/src/main/java/org/apache/hadoop/hbase/ipc/RpcClient.java * /hbase/branches/0.96/hbase-client/src/main/java/org/apache/hadoop/hbase/security/User.java * /hbase/branches/0.96/hbase-common/pom.xml * /hbase/branches/0.96/hbase-common/src/main/java/org/apache/hadoop/hbase/BaseConfigurable.java * /hbase/branches/0.96/hbase-common/src/main/java/org/apache/hadoop/hbase/security * /hbase/branches/0.96/hbase-common/src/main/java/org/apache/hadoop/hbase/security/User.java * /hbase/branches/0.96/hbase-common/src/main/java/org/apache/hadoop/hbase/security/UserProvider.java * /hbase/branches/0.96/hbase-server/src/main/java/org/apache/hadoop/hbase/BaseConfigurable.java * /hbase/branches/0.96/hbase-server/src/main/java/org/apache/hadoop/hbase/ipc/RpcServer.java * /hbase/branches/0.96/hbase-server/src/main/java/org/apache/hadoop/hbase/mapred/TableMapReduceUtil.java * /hbase/branches/0.96/hbase-server/src/main/java/org/apache/hadoop/hbase/mapreduce/LoadIncrementalHFiles.java * /hbase/branches/0.96/hbase-server/src/main/java/org/apache/hadoop/hbase/mapreduce/TableMapReduceUtil.java * /hbase/branches/0.96/hbase-server/src/main/java/org/apache/hadoop/hbase/master/HMaster.java * /hbase/branches/0.96/hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/HRegionServer.java * /hbase/branches/0.96/hbase-server/src/main/java/org/apache/hadoop/hbase/rest/RESTServer.java * /hbase/branches/0.96/hbase-server/src/main/java/org/apache/hadoop/hbase/rest/RESTServlet.java * /hbase/branches/0.96/hbase-server/src/main/java/org/apache/hadoop/hbase/security/access/AccessController.java * /hbase/branches/0.96/hbase-server/src/main/java/org/apache/hadoop/hbase/security/access/SecureBulkLoadEndpoint.java * /hbase/branches/0.96/hbase-server/src/main/java/org/apache/hadoop/hbase/security/access/TableAuthManager.java * /hbase/branches/0.96/hbase-server/src/main/java/org/apache/hadoop/hbase/util/HBaseFsck.java * /hbase/branches/0.96/hbase-server/src/test/java/org/apache/hadoop/hbase/mapreduce/HadoopSecurityEnabledUserProviderForTesting.java * /hbase/branches/0.96/hbase-server/src/test/java/org/apache/hadoop/hbase/mapreduce/TestLoadIncrementalHFiles.java * /hbase/branches/0.96/hbase-server/src/test/java/org/apache/hadoop/hbase/mapreduce/TestLoadIncrementalHFilesSplitRecovery.java * /hbase/branches/0.96/hbase-server/src/test/java/org/apache/hadoop/hbase/mapreduce/TestSecureLoadIncrementalHFiles.java * /hbase/branches/0.96/hbase-server/src/test/java/org/apache/hadoop/hbase/mapreduce/TestSecureLoadIncrementalHFilesSplitRecovery.java * /hbase/branches/0.96/hbase-thrift/src/main/java/org/apache/hadoop/hbase/thrift/ThriftServer.java Provide interface for getting a User in the client -- Key: HBASE-9221 URL: https://issues.apache.org/jira/browse/HBASE-9221 Project: HBase Issue Type: Improvement Components: Client, hadoop2, security Affects Versions: 0.98.0, 0.95.2, 0.94.12 Reporter: Jesse Yates Assignee: Jesse Yates Fix For: 0.98.0, 0.94.13, 0.96.1 Attachments: hbase-9221-0.94-v0.patch, hbase-9221-0.94-v1.patch, hbase-9221-0.94-v3.patch, hbase-9221-0.94-v4.patch, hbase-9221-0.96-trunk.addendum, hbase-9221-0.96-v0.patch, hbase-9221-0.96-v1.patch, hbase-9221-trunk-v0.patch, hbase-9221-trunk-v1.patch, hbase-9221-trunk-v2.patch, hbase-9221-trunk-v3.patch, hbase-9221-trunk-v4.patch, hbase-9221-trunk-v5.patch Sometimes, users will want to provide their own User class depending on the type of security they will support in their local environment. For instance, running Hadoop1 vs Hadoop2 vs CDH means potentially different ways of getting the UserGroupInformation. This issue abstracts out the mechanism by which we obtain an o.a.h.hbase.security.User to a UserProvider. This UserProvider can then be extented as a Hadoop 1/2 shim as well as supporting custom authentication code. -- This
[jira] [Commented] (HBASE-9221) Provide interface for getting a User in the client
[ https://issues.apache.org/jira/browse/HBASE-9221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13807480#comment-13807480 ] Jesse Yates commented on HBASE-9221: default is the current behavior - we will always do as we have done, unless you make your own class to do something else. That should just be a module move for the user class. HBaseProto was not intended, fixed in next patch. Provide interface for getting a User in the client -- Key: HBASE-9221 URL: https://issues.apache.org/jira/browse/HBASE-9221 Project: HBase Issue Type: Improvement Components: Client, hadoop2, security Affects Versions: 0.98.0, 0.95.2, 0.94.12 Reporter: Jesse Yates Assignee: Jesse Yates Fix For: 0.98.0, 0.96.1, 0.94.14 Attachments: hbase-9221-0.94-v0.patch, hbase-9221-0.94-v1.patch, hbase-9221-trunk-v0.patch, hbase-9221-trunk-v1.patch, hbase-9221-trunk-v2.patch, hbase-9221-trunk-v3.patch Sometimes, users will want to provide their own User class depending on the type of security they will support in their local environment. For instance, running Hadoop1 vs Hadoop2 vs CDH means potentially different ways of getting the UserGroupInformation. This issue abstracts out the mechanism by which we obtain an o.a.h.hbase.security.User to a UserProvider. This UserProvider can then be extented as a Hadoop 1/2 shim as well as supporting custom authentication code. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (HBASE-9221) Provide interface for getting a User in the client
[
https://issues.apache.org/jira/browse/HBASE-9221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13807525#comment-13807525
]
Lars Hofhansl commented on HBASE-9221:
--
Looks good. Are the LoadIncrementalHFiles change backward compatible. Looks
like they would be, just making sure.
Only tests use {{LoadIncrementalHFiles(Configuration conf, Boolean useSecure)}}?
Provide interface for getting a User in the client
--
Key: HBASE-9221
URL: https://issues.apache.org/jira/browse/HBASE-9221
Project: HBase
Issue Type: Improvement
Components: Client, hadoop2, security
Affects Versions: 0.98.0, 0.95.2, 0.94.12
Reporter: Jesse Yates
Assignee: Jesse Yates
Fix For: 0.98.0, 0.96.1, 0.94.14
Attachments: hbase-9221-0.94-v0.patch, hbase-9221-0.94-v1.patch,
hbase-9221-0.94-v3.patch, hbase-9221-0.96-v0.patch,
hbase-9221-trunk-v0.patch, hbase-9221-trunk-v1.patch,
hbase-9221-trunk-v2.patch, hbase-9221-trunk-v3.patch,
hbase-9221-trunk-v4.patch
Sometimes, users will want to provide their own User class depending on the
type of security they will support in their local environment. For instance,
running Hadoop1 vs Hadoop2 vs CDH means potentially different ways of getting
the UserGroupInformation.
This issue abstracts out the mechanism by which we obtain an
o.a.h.hbase.security.User to a UserProvider. This UserProvider can then be
extented as a Hadoop 1/2 shim as well as supporting custom authentication
code.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
[jira] [Commented] (HBASE-9221) Provide interface for getting a User in the client
[ https://issues.apache.org/jira/browse/HBASE-9221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13807535#comment-13807535 ] Jesse Yates commented on HBASE-9221: As far as I know, that's the only usage of it. Its package private for testing (and is commented as such), so it seemed ok. Managed in the tests now (for instance, TestSecureLoadIncrementalHFiles) by just setting the right config values. Offline mentioned the same to Lars and he is happy with the patch :) Planning to commit this evening, unless there are objections. Provide interface for getting a User in the client -- Key: HBASE-9221 URL: https://issues.apache.org/jira/browse/HBASE-9221 Project: HBase Issue Type: Improvement Components: Client, hadoop2, security Affects Versions: 0.98.0, 0.95.2, 0.94.12 Reporter: Jesse Yates Assignee: Jesse Yates Fix For: 0.98.0, 0.96.1, 0.94.14 Attachments: hbase-9221-0.94-v0.patch, hbase-9221-0.94-v1.patch, hbase-9221-0.94-v3.patch, hbase-9221-0.96-v0.patch, hbase-9221-trunk-v0.patch, hbase-9221-trunk-v1.patch, hbase-9221-trunk-v2.patch, hbase-9221-trunk-v3.patch, hbase-9221-trunk-v4.patch Sometimes, users will want to provide their own User class depending on the type of security they will support in their local environment. For instance, running Hadoop1 vs Hadoop2 vs CDH means potentially different ways of getting the UserGroupInformation. This issue abstracts out the mechanism by which we obtain an o.a.h.hbase.security.User to a UserProvider. This UserProvider can then be extented as a Hadoop 1/2 shim as well as supporting custom authentication code. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (HBASE-9221) Provide interface for getting a User in the client
[
https://issues.apache.org/jira/browse/HBASE-9221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13807581#comment-13807581
]
Hadoop QA commented on HBASE-9221:
--
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12610732/hbase-9221-trunk-v4.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 17 new
or modified tests.
{color:green}+1 hadoop1.0{color}. The patch compiles against the hadoop
1.0 profile.
{color:green}+1 hadoop2.0{color}. The patch compiles against the hadoop
2.0 profile.
{color:red}-1 javadoc{color}. The javadoc tool appears to have generated 1
warning messages.
{color:red}-1 javac{color}. The applied patch generated 12 javac compiler
warnings (more than the trunk's current 4 warnings).
{color:green}+1 findbugs{color}. The patch does not introduce any new
Findbugs (version 1.3.9) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 lineLengths{color}. The patch does not introduce lines
longer than 100
{color:red}-1 site{color}. The patch appears to cause mvn site goal to
fail.
{color:red}-1 core tests{color}. The patch failed these unit tests:
org.apache.hadoop.hbase.security.access.TestAccessController
org.apache.hadoop.hbase.security.access.TestZKPermissionsWatcher
org.apache.hadoop.hbase.mapreduce.TestSecureLoadIncrementalHFiles
org.apache.hadoop.hbase.mapreduce.TestSecureLoadIncrementalHFilesSplitRecovery
org.apache.hadoop.hbase.security.access.TestAccessControlFilter
org.apache.hadoop.hbase.security.access.TestTablePermissions
{color:red}-1 core zombie tests{color}. There are 1 zombie test(s):
Test results:
https://builds.apache.org/job/PreCommit-HBASE-Build/7655//testReport/
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/7655//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-protocol.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/7655//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-thrift.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/7655//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-client.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/7655//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-examples.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/7655//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop1-compat.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/7655//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-prefix-tree.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/7655//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-common.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/7655//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-server.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/7655//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop-compat.html
Console output:
https://builds.apache.org/job/PreCommit-HBASE-Build/7655//console
This message is automatically generated.
Provide interface for getting a User in the client
--
Key: HBASE-9221
URL: https://issues.apache.org/jira/browse/HBASE-9221
Project: HBase
Issue Type: Improvement
Components: Client, hadoop2, security
Affects Versions: 0.98.0, 0.95.2, 0.94.12
Reporter: Jesse Yates
Assignee: Jesse Yates
Fix For: 0.98.0, 0.96.1, 0.94.14
Attachments: hbase-9221-0.94-v0.patch, hbase-9221-0.94-v1.patch,
hbase-9221-0.94-v3.patch, hbase-9221-0.96-v0.patch,
hbase-9221-trunk-v0.patch, hbase-9221-trunk-v1.patch,
hbase-9221-trunk-v2.patch, hbase-9221-trunk-v3.patch,
hbase-9221-trunk-v4.patch
Sometimes, users will want to provide their own User class depending on the
type of security they will support in their local environment. For instance,
running Hadoop1 vs Hadoop2 vs CDH means potentially different ways of getting
the UserGroupInformation.
This issue abstracts out the mechanism by which we obtain an
o.a.h.hbase.security.User to a UserProvider. This UserProvider can then be
extented as a Hadoop 1/2 shim as well as supporting custom authentication
code.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
[jira] [Commented] (HBASE-9221) Provide interface for getting a User in the client
[ https://issues.apache.org/jira/browse/HBASE-9221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13807589#comment-13807589 ] Jesse Yates commented on HBASE-9221: Hmm, looks like something with the SecureTestUtil. Going to hold off until I figure out if its related, but might not make it 0.94.13 release now (though it would be nice) Provide interface for getting a User in the client -- Key: HBASE-9221 URL: https://issues.apache.org/jira/browse/HBASE-9221 Project: HBase Issue Type: Improvement Components: Client, hadoop2, security Affects Versions: 0.98.0, 0.95.2, 0.94.12 Reporter: Jesse Yates Assignee: Jesse Yates Fix For: 0.98.0, 0.96.1, 0.94.14 Attachments: hbase-9221-0.94-v0.patch, hbase-9221-0.94-v1.patch, hbase-9221-0.94-v3.patch, hbase-9221-0.96-v0.patch, hbase-9221-trunk-v0.patch, hbase-9221-trunk-v1.patch, hbase-9221-trunk-v2.patch, hbase-9221-trunk-v3.patch, hbase-9221-trunk-v4.patch Sometimes, users will want to provide their own User class depending on the type of security they will support in their local environment. For instance, running Hadoop1 vs Hadoop2 vs CDH means potentially different ways of getting the UserGroupInformation. This issue abstracts out the mechanism by which we obtain an o.a.h.hbase.security.User to a UserProvider. This UserProvider can then be extented as a Hadoop 1/2 shim as well as supporting custom authentication code. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (HBASE-9221) Provide interface for getting a User in the client
[ https://issues.apache.org/jira/browse/HBASE-9221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13807699#comment-13807699 ] Lars Hofhansl commented on HBASE-9221: -- Let's have a look tomorrow morning. If we can't fix it, we'll get it in 3-4 weeks later. No big deal. Provide interface for getting a User in the client -- Key: HBASE-9221 URL: https://issues.apache.org/jira/browse/HBASE-9221 Project: HBase Issue Type: Improvement Components: Client, hadoop2, security Affects Versions: 0.98.0, 0.95.2, 0.94.12 Reporter: Jesse Yates Assignee: Jesse Yates Fix For: 0.98.0, 0.94.13, 0.96.1 Attachments: hbase-9221-0.94-v0.patch, hbase-9221-0.94-v1.patch, hbase-9221-0.94-v3.patch, hbase-9221-0.96-v0.patch, hbase-9221-trunk-v0.patch, hbase-9221-trunk-v1.patch, hbase-9221-trunk-v2.patch, hbase-9221-trunk-v3.patch, hbase-9221-trunk-v4.patch Sometimes, users will want to provide their own User class depending on the type of security they will support in their local environment. For instance, running Hadoop1 vs Hadoop2 vs CDH means potentially different ways of getting the UserGroupInformation. This issue abstracts out the mechanism by which we obtain an o.a.h.hbase.security.User to a UserProvider. This UserProvider can then be extented as a Hadoop 1/2 shim as well as supporting custom authentication code. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (HBASE-9221) Provide interface for getting a User in the client
[
https://issues.apache.org/jira/browse/HBASE-9221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13803283#comment-13803283
]
stack commented on HBASE-9221:
--
Patch looks good.
Any danger of this being the default; i.e. a new Connection each time?
+ * @param ticket Be careful which ticket you pass. A new user will mean a
new Connection.
+ * {@link UserProvider#getCurrent()} makes a new instance of User
each time so will be a
+ * new Connection each time.
Is that just a module move for the User class?
Is the remove of hbase-protocol/src/main/protobuf/HBase.proto intended?
Else patch lgtm.
Provide interface for getting a User in the client
--
Key: HBASE-9221
URL: https://issues.apache.org/jira/browse/HBASE-9221
Project: HBase
Issue Type: Improvement
Components: Client, hadoop2, security
Affects Versions: 0.98.0, 0.95.2, 0.94.12
Reporter: Jesse Yates
Assignee: Jesse Yates
Fix For: 0.98.0, 0.94.13, 0.96.1
Attachments: hbase-9221-0.94-v0.patch, hbase-9221-0.94-v1.patch,
hbase-9221-trunk-v0.patch, hbase-9221-trunk-v1.patch,
hbase-9221-trunk-v2.patch, hbase-9221-trunk-v3.patch
Sometimes, users will want to provide their own User class depending on the
type of security they will support in their local environment. For instance,
running Hadoop1 vs Hadoop2 vs CDH means potentially different ways of getting
the UserGroupInformation.
This issue abstracts out the mechanism by which we obtain an
o.a.h.hbase.security.User to a UserProvider. This UserProvider can then be
extented as a Hadoop 1/2 shim as well as supporting custom authentication
code.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
[jira] [Commented] (HBASE-9221) Provide interface for getting a User in the client
[ https://issues.apache.org/jira/browse/HBASE-9221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13800926#comment-13800926 ] Jesse Yates commented on HBASE-9221: Thought so, just haven't heard either way from anyone. I'll take a look today to see if they need rebasing. Provide interface for getting a User in the client -- Key: HBASE-9221 URL: https://issues.apache.org/jira/browse/HBASE-9221 Project: HBase Issue Type: Improvement Components: Client, hadoop2, security Affects Versions: 0.98.0, 0.95.2, 0.94.12 Reporter: Jesse Yates Assignee: Jesse Yates Fix For: 0.98.0, 0.94.13, 0.96.1 Attachments: hbase-9221-0.94-v0.patch, hbase-9221-0.94-v1.patch, hbase-9221-trunk-v0.patch, hbase-9221-trunk-v1.patch, hbase-9221-trunk-v2.patch, hbase-9221-trunk-v3.patch Sometimes, users will want to provide their own User class depending on the type of security they will support in their local environment. For instance, running Hadoop1 vs Hadoop2 vs CDH means potentially different ways of getting the UserGroupInformation. This issue abstracts out the mechanism by which we obtain an o.a.h.hbase.security.User to a UserProvider. This UserProvider can then be extented as a Hadoop 1/2 shim as well as supporting custom authentication code. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (HBASE-9221) Provide interface for getting a User in the client
[ https://issues.apache.org/jira/browse/HBASE-9221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13800238#comment-13800238 ] Lars Hofhansl commented on HBASE-9221: -- Is this done [~jesse_yates]? Provide interface for getting a User in the client -- Key: HBASE-9221 URL: https://issues.apache.org/jira/browse/HBASE-9221 Project: HBase Issue Type: Improvement Components: Client, hadoop2, security Affects Versions: 0.98.0, 0.95.2, 0.94.12 Reporter: Jesse Yates Assignee: Jesse Yates Fix For: 0.98.0, 0.94.13, 0.96.1 Attachments: hbase-9221-0.94-v0.patch, hbase-9221-0.94-v1.patch, hbase-9221-trunk-v0.patch, hbase-9221-trunk-v1.patch, hbase-9221-trunk-v2.patch, hbase-9221-trunk-v3.patch Sometimes, users will want to provide their own User class depending on the type of security they will support in their local environment. For instance, running Hadoop1 vs Hadoop2 vs CDH means potentially different ways of getting the UserGroupInformation. This issue abstracts out the mechanism by which we obtain an o.a.h.hbase.security.User to a UserProvider. This UserProvider can then be extented as a Hadoop 1/2 shim as well as supporting custom authentication code. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (HBASE-9221) Provide interface for getting a User in the client
[
https://issues.apache.org/jira/browse/HBASE-9221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13766137#comment-13766137
]
Hadoop QA commented on HBASE-9221:
--
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12602934/hbase-9221-trunk-v2.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 14 new
or modified tests.
{color:red}-1 patch{color}. The patch command could not apply the patch.
Console output:
https://builds.apache.org/job/PreCommit-HBASE-Build/7203//console
This message is automatically generated.
Provide interface for getting a User in the client
--
Key: HBASE-9221
URL: https://issues.apache.org/jira/browse/HBASE-9221
Project: HBase
Issue Type: Improvement
Components: Client, hadoop2, security
Affects Versions: 0.98.0, 0.95.2, 0.94.12
Reporter: Jesse Yates
Assignee: Jesse Yates
Fix For: 0.98.0, 0.94.13, 0.96.1
Attachments: hbase-9221-0.94-v0.patch, hbase-9221-0.94-v1.patch,
hbase-9221-trunk-v0.patch, hbase-9221-trunk-v1.patch,
hbase-9221-trunk-v2.patch
Sometimes, users will want to provide their own User class depending on the
type of security they will support in their local environment. For instance,
running Hadoop1 vs Hadoop2 vs CDH means potentially different ways of getting
the UserGroupInformation.
This issue abstracts out the mechanism by which we obtain an
o.a.h.hbase.security.User to a UserProvider. This UserProvider can then be
extented as a Hadoop 1/2 shim as well as supporting custom authentication
code.
--
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
[jira] [Commented] (HBASE-9221) Provide interface for getting a User in the client
[
https://issues.apache.org/jira/browse/HBASE-9221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13766224#comment-13766224
]
Hadoop QA commented on HBASE-9221:
--
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12602945/hbase-9221-trunk-v3.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 14 new
or modified tests.
{color:green}+1 hadoop1.0{color}. The patch compiles against the hadoop
1.0 profile.
{color:green}+1 hadoop2.0{color}. The patch compiles against the hadoop
2.0 profile.
{color:red}-1 javadoc{color}. The javadoc tool appears to have generated 1
warning messages.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:red}-1 findbugs{color}. The patch appears to introduce 1 new
Findbugs (version 1.3.9) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 lineLengths{color}. The patch does not introduce lines
longer than 100
{color:green}+1 site{color}. The mvn site goal succeeds with this patch.
{color:red}-1 core tests{color}. The patch failed these unit tests:
org.apache.hadoop.hbase.mapreduce.TestSecureLoadIncrementalHFiles
org.apache.hadoop.hbase.security.access.TestTablePermissions
org.apache.hadoop.hbase.security.access.TestZKPermissionsWatcher
org.apache.hadoop.hbase.security.access.TestAccessControlFilter
org.apache.hadoop.hbase.mapreduce.TestSecureLoadIncrementalHFilesSplitRecovery
org.apache.hadoop.hbase.security.access.TestAccessController
{color:red}-1 core zombie tests{color}. There are 1 zombie test(s):
Test results:
https://builds.apache.org/job/PreCommit-HBASE-Build/7204//testReport/
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/7204//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-prefix-tree.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/7204//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-client.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/7204//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-common.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/7204//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-protocol.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/7204//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-server.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/7204//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop1-compat.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/7204//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-examples.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/7204//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop-compat.html
Console output:
https://builds.apache.org/job/PreCommit-HBASE-Build/7204//console
This message is automatically generated.
Provide interface for getting a User in the client
--
Key: HBASE-9221
URL: https://issues.apache.org/jira/browse/HBASE-9221
Project: HBase
Issue Type: Improvement
Components: Client, hadoop2, security
Affects Versions: 0.98.0, 0.95.2, 0.94.12
Reporter: Jesse Yates
Assignee: Jesse Yates
Fix For: 0.98.0, 0.94.13, 0.96.1
Attachments: hbase-9221-0.94-v0.patch, hbase-9221-0.94-v1.patch,
hbase-9221-trunk-v0.patch, hbase-9221-trunk-v1.patch,
hbase-9221-trunk-v2.patch, hbase-9221-trunk-v3.patch
Sometimes, users will want to provide their own User class depending on the
type of security they will support in their local environment. For instance,
running Hadoop1 vs Hadoop2 vs CDH means potentially different ways of getting
the UserGroupInformation.
This issue abstracts out the mechanism by which we obtain an
o.a.h.hbase.security.User to a UserProvider. This UserProvider can then be
extented as a Hadoop 1/2 shim as well as supporting custom authentication
code.
--
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
[jira] [Commented] (HBASE-9221) Provide interface for getting a User in the client
[
https://issues.apache.org/jira/browse/HBASE-9221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13766059#comment-13766059
]
Hadoop QA commented on HBASE-9221:
--
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12602916/hbase-9221-trunk-v1.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 14 new
or modified tests.
{color:red}-1 patch{color}. The patch command could not apply the patch.
Console output:
https://builds.apache.org/job/PreCommit-HBASE-Build/7202//console
This message is automatically generated.
Provide interface for getting a User in the client
--
Key: HBASE-9221
URL: https://issues.apache.org/jira/browse/HBASE-9221
Project: HBase
Issue Type: Improvement
Components: Client, hadoop2, security
Affects Versions: 0.98.0, 0.95.2, 0.94.12
Reporter: Jesse Yates
Assignee: Jesse Yates
Fix For: 0.98.0, 0.94.13, 0.96.1
Attachments: hbase-9221-0.94-v0.patch, hbase-9221-0.94-v1.patch,
hbase-9221-trunk-v0.patch, hbase-9221-trunk-v1.patch
Sometimes, users will want to provide their own User class depending on the
type of security they will support in their local environment. For instance,
running Hadoop1 vs Hadoop2 vs CDH means potentially different ways of getting
the UserGroupInformation.
This issue abstracts out the mechanism by which we obtain an
o.a.h.hbase.security.User to a UserProvider. This UserProvider can then be
extented as a Hadoop 1/2 shim as well as supporting custom authentication
code.
--
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
[jira] [Commented] (HBASE-9221) Provide interface for getting a User in the client
[
https://issues.apache.org/jira/browse/HBASE-9221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13760861#comment-13760861
]
Hadoop QA commented on HBASE-9221:
--
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12601950/hbase-9221-trunk-v0.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 14 new
or modified tests.
{color:green}+1 hadoop1.0{color}. The patch compiles against the hadoop
1.0 profile.
{color:red}-1 hadoop2.0{color}. The patch failed to compile against the
hadoop 2.0 profile.
Console output:
https://builds.apache.org/job/PreCommit-HBASE-Build/7080//console
This message is automatically generated.
Provide interface for getting a User in the client
--
Key: HBASE-9221
URL: https://issues.apache.org/jira/browse/HBASE-9221
Project: HBase
Issue Type: Improvement
Components: Client, hadoop2, security
Affects Versions: 0.98.0, 0.95.2, 0.94.12
Reporter: Jesse Yates
Assignee: Jesse Yates
Fix For: 0.98.0, 0.94.12, 0.96.1
Attachments: hbase-9221-0.94-v0.patch, hbase-9221-0.94-v1.patch,
hbase-9221-trunk-v0.patch
Sometimes, users will want to provide their own User class depending on the
type of security they will support in their local environment. For instance,
running Hadoop1 vs Hadoop2 vs CDH means potentially different ways of getting
the UserGroupInformation.
This issue abstracts out the mechanism by which we obtain an
o.a.h.hbase.security.User to a UserProvider. This UserProvider can then be
extented as a Hadoop 1/2 shim as well as supporting custom authentication
code.
--
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
[jira] [Commented] (HBASE-9221) Provide interface for getting a User in the client
[ https://issues.apache.org/jira/browse/HBASE-9221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13740370#comment-13740370 ] Jesse Yates commented on HBASE-9221: This came up at Salesforce where we have to connect to a secure and insecure cluster from the same JVM. To enable this, we needed to rewrite UserGroupInformation to correctly support this case. However, this meant we needed to change how we obtain a o.a.h.h.security.User (to bind it to the right Configuration). Provide interface for getting a User in the client -- Key: HBASE-9221 URL: https://issues.apache.org/jira/browse/HBASE-9221 Project: HBase Issue Type: Improvement Components: Client, hadoop2, security Affects Versions: 0.98.0, 0.95.2, 0.94.12 Reporter: Jesse Yates Assignee: Jesse Yates Sometimes, users will want to provide their own User class depending on the type of security they will support in their local environment. For instance, running Hadoop1 vs Hadoop2 vs CDH means potentially different ways of getting the UserGroupInformation. This issue abstracts out the mechanism by which we obtain an o.a.h.hbase.security.User to a UserProvider. This UserProvider can then be extented as a Hadoop 1/2 shim as well as supporting custom authentication code. -- 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
[jira] [Commented] (HBASE-9221) Provide interface for getting a User in the client
[ https://issues.apache.org/jira/browse/HBASE-9221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13740585#comment-13740585 ] Andrew Purtell commented on HBASE-9221: --- +1 There are Hadoop JIRAs active now on refactoring UGI. One is HADOOP-9797. Provide interface for getting a User in the client -- Key: HBASE-9221 URL: https://issues.apache.org/jira/browse/HBASE-9221 Project: HBase Issue Type: Improvement Components: Client, hadoop2, security Affects Versions: 0.98.0, 0.95.2, 0.94.12 Reporter: Jesse Yates Assignee: Jesse Yates Attachments: hbase-9221-0.94-v0.patch Sometimes, users will want to provide their own User class depending on the type of security they will support in their local environment. For instance, running Hadoop1 vs Hadoop2 vs CDH means potentially different ways of getting the UserGroupInformation. This issue abstracts out the mechanism by which we obtain an o.a.h.hbase.security.User to a UserProvider. This UserProvider can then be extented as a Hadoop 1/2 shim as well as supporting custom authentication code. -- 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
[jira] [Commented] (HBASE-9221) Provide interface for getting a User in the client
[ https://issues.apache.org/jira/browse/HBASE-9221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13740698#comment-13740698 ] stack commented on HBASE-9221: -- You have a patch [~jesse_yates]? Provide interface for getting a User in the client -- Key: HBASE-9221 URL: https://issues.apache.org/jira/browse/HBASE-9221 Project: HBase Issue Type: Improvement Components: Client, hadoop2, security Affects Versions: 0.98.0, 0.95.2, 0.94.12 Reporter: Jesse Yates Assignee: Jesse Yates Attachments: hbase-9221-0.94-v0.patch Sometimes, users will want to provide their own User class depending on the type of security they will support in their local environment. For instance, running Hadoop1 vs Hadoop2 vs CDH means potentially different ways of getting the UserGroupInformation. This issue abstracts out the mechanism by which we obtain an o.a.h.hbase.security.User to a UserProvider. This UserProvider can then be extented as a Hadoop 1/2 shim as well as supporting custom authentication code. -- 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
