[jira] [Commented] (LENS-1192) Support configuring multiple connection pools for JDBC query executions

["Puneet Gupta (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/LENS-1192?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15335337#comment-15335337 ] 

Puneet Gupta commented on LENS-1192:
------------------------------------

We would also need to see how to throttle such queries which are executed on same driver but belong to different groups.

Also wondering if we can solve this easily by having two different drivers( both hosting same schema but the final driver choice is made based on the query group). In this case we would need to optimize the query planning as both drivers will essentially generate same plan and that would be wasteful.

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