GitHub user prasadwagle reopened a pull request:
https://github.com/apache/zeppelin/pull/1240
[ZEPPELIN-1246] In JDBCInterpreter.getScheduler, use
getMaxConcurrentConnection instead of hardcoding maxConcurrency to 10
### What is this PR for?
In JDBCInterpreter.getScheduler, use getMaxConcurrentConnection instead of
hardcoding maxConcurrency to 10
### What type of PR is it?
Improvement
### Todos
* [ ] - Task
### What is the Jira issue?
[ZEPPELIN-1246] (https://issues.apache.org/jira/browse/ZEPPELIN-1246)
### How should this be tested?
Set zeppelin.jdbc.concurrent.max_connection to 2 and verify after starting
two long-running queries, a third query is pending.
### 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/prasadwagle/incubator-zeppelin ZEPPELIN-1246
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/zeppelin/pull/1240.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 #1240
----
commit 4b2990fe89e6fcc37c9de5839443ed9edc9e48ef
Author: Prasad Wagle <pwa...@twitter.com>
Date: 2016-07-28T21:27:15Z
In JDBCInterpreter.getScheduler, use getMaxConcurrentConnection instead of
hardcoding maxConcurrency to 10
----
---
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.
---
