You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lens.apache.org by "Puneet Gupta (JIRA)" <ji...@apache.org> on 2016/06/17 03:35:06 UTC
[jira] [Created] (LENS-1192) Support configuring multiple
connection pools for JDBC query executions
Puneet Gupta created LENS-1192:
----------------------------------
Summary: Support configuring multiple connection pools for JDBC query executions
Key: LENS-1192
URL: https://issues.apache.org/jira/browse/LENS-1192
Project: Apache Lens
Issue Type: New Feature
Reporter: Puneet Gupta
The use case is something like this .
There are two types of uses for JDBC queries
1. Human users who have tighter SLA's.
2. Apps like alerting systems built on top on lens, these have longer SLA's and are also capable of flooding the lens server with automatically generated requests in bulk.
From DB side, the DB admin also wants to segregate the resources allocated for the two different group of users. Group1 is more critical and will have more resources. The queries hitting DB under Group2 would have less resources and would be isolated from Group1 and hence would not affect the performance of Group1 queries.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)