You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@phoenix.apache.org by "James Taylor (JIRA)" <ji...@apache.org> on 2016/08/02 07:33:20 UTC

[jira] [Comment Edited] (PHOENIX-3126) The driver implementation should take into account the context of the user

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

James Taylor edited comment on PHOENIX-3126 at 8/2/16 7:32 AM:
---------------------------------------------------------------

Phoenix will share the same HConnection from the same JVM if the connection URL is the same. This patch prevents that sharing if the {{User.getCurrent()}} is different.


was (Author: jamestaylor):
Phoenix will share the same HConnection if the connection URL is the same. This patch prevents that sharing if the {{User.getCurrent()}} is different.

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