GitHub user astroshim reopened a pull request:

    [ZEPPELIN-1405] ConnectionPool for JDBCInterpreter.

    ### What is this PR for?
    This PR is for refactoring code for JDBCInterpreter.
    There is no putting 'Connection' to 'propertyKeyUnusedConnectionListMap' 
anywhere in the original code.
    ### What type of PR is it?
    ### What is the Jira issue?
    ### 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 ZEPPELIN-1405

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 #1396
commit 12dd7cb239cd22cb85d55221a18bbf157665a45a
Author: astroshim <>
Date:   2016-09-02T09:05:50Z

    remove propertyKeyUnusedConnectionListMap map

commit 4dabbcc98d5f8e8013502ba786ec7f60f115efff
Author: astroshim <>
Date:   2016-09-04T18:08:36Z

    wip) changing to use dbcp

commit 9f1e368fe16ef889715b8a58e9592cb0393ae464
Author: astroshim <>
Date:   2016-09-05T15:58:25Z

    replace ConnectionPool

commit 4d4f85cf1e59aaecbabe025b6c261349c94abe4a
Author: astroshim <>
Date:   2016-09-05T16:10:41Z

    refactoring code of close()

commit 21217a7340438bbd39b75a1dd3756885c4d2d911
Author: astroshim <>
Date:   2016-09-07T02:06:50Z

    fix indentation.

commit efc2bfc2c590ea6ccc3ca99490e326f25a3aa3c4
Author: astroshim <>
Date:   2016-09-12T14:53:09Z


commit 1862ae6c694681861a6e51f26960b61478c6df4d
Author: astroshim <>
Date:   2016-09-21T12:58:38Z

    Merge branch 'master' into ZEPPELIN-1405

commit f6998c27ddad2bd93d48a3acbdfca24c698095d6
Author: astroshim <>
Date:   2016-09-22T12:52:35Z

    Merge branch 'master' into ZEPPELIN-1405


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

Reply via email to