[
https://issues.apache.org/jira/browse/PHOENIX-3126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15405084#comment-15405084
]
Hudson commented on PHOENIX-3126:
---------------------------------
FAILURE: Integrated in Phoenix-master #1350 (See
[https://builds.apache.org/job/Phoenix-master/1350/])
PHOENIX-3126 Tie a driver instance to a specific user (Prabhjyot Singh)
(elserj: rev a9ea8a3baa32714a1640c1197609910863daca79)
* phoenix-core/src/main/java/org/apache/phoenix/jdbc/PhoenixEmbeddedDriver.java
> The driver implementation should take into account the context of the user
> --------------------------------------------------------------------------
>
> Key: PHOENIX-3126
> URL: https://issues.apache.org/jira/browse/PHOENIX-3126
> Project: Phoenix
> Issue Type: Bug
> Reporter: Devaraj Das
> Assignee: Prabhjyot Singh
> Fix For: 4.8.0
>
> Attachments: PHOENIX-3126.2.txt, PHOENIX-3126.txt, aaaa.java
>
>
> Ran into this issue ...
> We have an application that proxies various users internally and fires
> queries for those users. The Phoenix driver implementation caches connections
> it successfully creates and keys it by the ConnectionInfo. The ConnectionInfo
> doesn't take into consideration the "user". So random users (including those
> that aren't supposed to access) can access the tables in this sort of a setup.
> The fix is to also consider the User in the ConnectionInfo.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
