[
https://issues.apache.org/jira/browse/LENS-922?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15095651#comment-15095651
]
piyush commented on LENS-922:
-----------------------------
sol1.
we can decouple the session and jdbc connection.
regardless of the connection we have session per new users.
1. Current db will be property of logged in user and not with the jdbc
connection.
2. Used resources( jar and files ) will be property of logged in user and no
more controlled by jdbc connection.
3. Close of connection won’t close all opened session as the session can be
used by user from some other connection
sol 2 .
we can have session per combination of user and jdbc connection.
for example :
we will create session if user1 log in and uses connection1.
and then we are a different session if user1 login with connection2.
> [client JDBC] lens session is shared by many users.
> ---------------------------------------------------
>
> Key: LENS-922
> URL: https://issues.apache.org/jira/browse/LENS-922
> Project: Apache Lens
> Issue Type: Improvement
> Reporter: piyush
>
> In current lens jdbc client:
> lens session is attached with jdbc connection.
> most of the application create jdbc connection pool and connection
> can be reused by multiple users. so effectively multiple users will share
> the the single connection and hence the lens session.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
