[GitHub] zeppelin pull request #2417: Add credential to spark interpreter

classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
Report Content as Inappropriate

[GitHub] zeppelin pull request #2417: Add credential to spark interpreter

GitHub user buptljy opened a pull request:


    Add  credential to spark interpreter

    ### What is this PR for?
          If we want to access databases in a spark interpreter, we need to specify our own private username and password in a spark interpreter paragraph, which is not always safe due to visible authentifier information.
    ### What type of PR is it?
    [ Improvement ]
    ### What is the Jira issue?
    * [ ZEPPELIN-2660 | https://issues.apache.org/jira/browse/ZEPPELIN-2660]
    ### How should this be tested?
    * Create a new spark interpreter paragraph
    * use userCredentials.get("your entity").get("username") to get username
    * user userCredentials.get("your entity").get("password") to get password
    ### Questions:
    * Does this needs documentation?

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

    $ git pull https://github.com/buptljy/zeppelin wind_master_dev

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


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

    This closes #2417
commit 5cac6633c8ca8647fa45fa882ed65ec8a2658443
Author: Liao Jiayi <[hidden email]>
Date:   2017-06-16T06:43:01Z

    add credential in spark interpreter

commit b53d10db9d046db4070d1fd84dde4fc98f202053
Author: Liao Jiayi <[hidden email]>
Date:   2017-06-16T07:27:55Z

    Testing Travis CI

commit 0d30088928e4e8b4baf4edd81741729f517bfcba
Author: Liao Jiayi <[hidden email]>
Date:   2017-06-16T08:00:12Z

    remove NewUser.txt


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 [hidden email] or file a JIRA ticket
with INFRA.