GitHub user wjsl opened a pull request:

    https://github.com/apache/accumulo/pull/119

    ACCUMULO-4348 Deprecate KerberosToken constructor with side effects

    `KerberosToken(String, File, boolean)` is deprecated in favor of 
`KerberosToken(String, File)`.
    
    The boolean flag would log in the requested user with Hadoop's 
`UserGroupInformation` class. This
    changed global state about who the active user was. In a multi-user 
environment, this potentially
    made little sense as other users could overwrite eachother.
    
    This patch includes a convenience constructor that doesn't have any side 
effects, but has the same
    semantics as logging in a user with a keytab.

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/wjsl/accumulo ACCUMULO-4348

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/accumulo/pull/119.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #119
    
----
commit 0e585904163f4227705d0ca42c188f0526b3ef49
Author: Bill Slacum <[email protected]>
Date:   2016-06-21T19:26:07Z

    ACCUMULO-4348 Deprecate KerberosToken constructor with side effects
    
    `KerberosToken(String, File, boolean)` is deprecated in favor of 
`KerberosToken(String, File)`.
    
    The boolean flag would log in the requested user with Hadoop's 
`UserGroupInformation` class. This
    changed global state about who the active user was. In a multi-user 
environment, this potentially
    made little sense as other users could overwrite eachother.
    
    This patch includes a convenience constructor that doesn't have any side 
effects, but has the same
    semantics as logging in a user with a keytab.

----


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---

Reply via email to