GitHub user 1ambda reopened a pull request:

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

    [ZEPPELIN-1650] Add mariadb, redshift configs and useful links to JDBC doc

    ### What is this PR for?
    
    Add 2 JDBC configs and useful links to JDBC doc so that users can connect 
those backends easily :)
    
    
    ### What type of PR is it?
    
    Documentation
    
    ### Todos
    * [ ] - Task
    
    ### What is the Jira issue?
    
    [ZEPPELIN-1650](https://issues.apache.org/jira/browse/ZEPPELIN-1650)
    
    ### How should this be tested?
    
    See screenshots.
    
    ### Screenshots (if appropriate)
    
    <img width="706" alt="example_redshift" 
src="https://cloud.githubusercontent.com/assets/4968473/20208653/01b1e468-a833-11e6-9166-b05d15e9a5fe.png";>
    <img width="577" alt="example_mariadb" 
src="https://cloud.githubusercontent.com/assets/4968473/20208654/02b49a22-a833-11e6-9b29-5a61f2b6a4bb.png";>
    
    
    ### 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/1ambda/zeppelin jdbc-doc-improve

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

    https://github.com/apache/zeppelin/pull/1621.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 #1621
    
----
commit 2fb5db15ad5906a16cfe6fd908526cfc098eba11
Author: 1ambda <1am...@gmail.com>
Date:   2016-11-11T08:12:03Z

    docs: Add mariadb, redshift configs

commit ce24af174cab58278d6cd8647f7c60c15788ac62
Author: AhyoungRyu <fbdkdu...@hanmail.net>
Date:   2016-11-11T17:13:20Z

    Make mariadb and redshift screenshots same with others

commit 6009eb9c88d7faefead819fa735a75b265d00221
Author: 1ambda <1am...@gmail.com>
Date:   2016-11-12T03:28:25Z

    docs: Add postgres section, hive2 doc link
    
    Don't make users confused when seperated postgre doc is removed

----


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