GitHub user astroshim reopened a pull request:

    https://github.com/apache/zeppelin/pull/1539

    [ZEPPELIN-1567] Let JDBC interpreter use user credential information.

    ### What is this PR for?
    
    This PR is for the multi-tenant of JDBC Interpreter.
    
    User can create a user/password for JDBC account at the [Credential 
page](http://zeppelin.apache.org/docs/0.7.0-SNAPSHOT/security/datasource_authorization.html).
    The `Entity` of `Credential` is match with JDBC interpreter group name.
    
    If the account for JDBC is not setted in the `Interpreter property` then 
use `Credential`'s.  
    ### What type of PR is it?
    
    Improvement
    ### What is the Jira issue?
    
    https://issues.apache.org/jira/browse/ZEPPELIN-1567
    ### How should this be tested?
    
    Please refer to testMultiTenant() of JDBCInterpreterTest/
    ### Screenshots (if appropriate)
    ### Questions:
    - Does the licenses files need update? no
    - Is there breaking changes for older versions? no
    - Does this needs documentation? no


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

    $ git pull https://github.com/astroshim/zeppelin jdbc-impersonation

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

    https://github.com/apache/zeppelin/pull/1539.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 #1539
    
----
commit 373d5f1018488ab435d817551f2b628258cc42b9
Author: astroshim <hss...@nflabs.com>
Date:   2016-10-18T10:53:26Z

    pass replName to Interpreter and use credential info for jdbc auth.

commit 3dafdf017c9b1cdb04565d8132e48a18942ea971
Author: astroshim <hss...@nflabs.com>
Date:   2016-10-18T15:14:59Z

    add testcase

commit 91619374be06fadd9608d02a7e13d347ad9e0a07
Author: astroshim <hss...@nflabs.com>
Date:   2016-10-18T15:15:40Z

    clean code

commit 722e333fe47c007a0252f744d5a3173613bed50f
Author: astroshim <hss...@nflabs.com>
Date:   2016-10-18T16:25:59Z

    change testcase name

commit f311f34aa6ac3fc9e3830e1a5ae650cc69e15f84
Author: astroshim <hss...@nflabs.com>
Date:   2016-10-19T04:02:23Z

    fix typo

commit 6573c1c68b7281f4792251e89d6e4f54ed7ad966
Author: astroshim <hss...@nflabs.com>
Date:   2016-10-19T04:14:05Z

    change variable name

commit 63d6a1c7d945b7edb6b297980e98dc5ca5620cf9
Author: astroshim <hss...@nflabs.com>
Date:   2016-10-19T12:09:02Z

    change thrift version to 0.9.2

commit df1b1dcae81a3e88f007979cae2a6d2c2444eb13
Author: astroshim <hss...@nflabs.com>
Date:   2016-10-29T06:26:15Z

    rebase and entity name convention.

commit df80741e460d27f658e182a192464b0efa3f9b6f
Author: astroshim <hss...@nflabs.com>
Date:   2016-10-30T06:48:21Z

    documentation for credential.

commit a305eca1d0fdd4404079d8fbb0169b1837da996f
Author: astroshim <hss...@nflabs.com>
Date:   2016-10-30T06:55:55Z

    Merge branch 'master' into jdbc-impersonation

commit fee70862fc8069a91f80dccea94011f2ad2a261a
Author: astroshim <hss...@nflabs.com>
Date:   2016-10-30T08:41:20Z

    fix build error.

commit 34fe0a67732dfad02d20322f40b0e10e8f2f166f
Author: astroshim <hss...@nflabs.com>
Date:   2016-10-30T08:47:24Z

    fix code for more simple.

commit 086dfdab58c477790b5a19b1d983191eaeaef5ee
Author: astroshim <hss...@nflabs.com>
Date:   2016-10-30T14:26:50Z

    fix testcase

commit 24a82260adac1179beec8668df9adc731fff747d
Author: astroshim <hss...@nflabs.com>
Date:   2016-10-31T05:21:22Z

    fix doc

commit b55aceb8afc26ed8d82b07e4524d40cc899d9528
Author: astroshim <hss...@nflabs.com>
Date:   2016-11-05T12:10:21Z

    Merge branch 'master' into jdbc-impersonation

commit 99621818aebdbc5161cbc5d90fac37287dddbda2
Author: astroshim <hss...@nflabs.com>
Date:   2016-11-05T13:41:58Z

    fix InterpreterOutput of PySparkInterpreterTest case

----


---
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 infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Reply via email to