GitHub user ash211 opened a pull request:

    https://github.com/apache/spark/pull/2286

    Don't include the empty string "" as a defaultAclUser

    Changes logging from
    
    ```
    14/09/05 02:01:08 INFO SecurityManager: Changing view acls to: aash,
    14/09/05 02:01:08 INFO SecurityManager: Changing modify acls to: aash,
    14/09/05 02:01:08 INFO SecurityManager: SecurityManager: authentication 
disabled; ui acls disabled; users with view permissions: Set(aash, ); users 
with modify permissions: Set(aash, )
    ```
    to
    ```
    14/09/05 02:28:28 INFO SecurityManager: Changing view acls to: aash
    14/09/05 02:28:28 INFO SecurityManager: Changing modify acls to: aash
    14/09/05 02:28:28 INFO SecurityManager: SecurityManager: authentication 
disabled; ui acls disabled; users with view permissions: Set(aash); users with 
modify permissions: Set(aash)
    ```
    
    Note that the first set of logs have a Set of size 2 containing "aash" and 
the empty string ""
    
    cc @tgravescs

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

    $ git pull https://github.com/ash211/spark empty-default-acl

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

    https://github.com/apache/spark/pull/2286.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 #2286
    
----
commit cf973a1b8f202cd7fe70cf60c701c62c51d2e702
Author: Andrew Ash <[email protected]>
Date:   2014-09-05T09:30:33Z

    Don't include the empty string "" as a defaultAclUser

----


---
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.
---

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to