[
https://issues.apache.org/jira/browse/PHOENIX-3126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15398523#comment-15398523
]
James Taylor edited comment on PHOENIX-3126 at 7/29/16 1:02 AM:
----------------------------------------------------------------
Thanks, [~devaraj] & [~prabhjot]. Is it possible that {{User.getCurrent()}}
returns null (in which case we'll need to guard against this in the hashcode
method)? Would be ever want different users to share the same underlying
HConnection? How many different users might be on the same JVM?
[~apurtell] - what do you think?
Also, do you consider this a blocker for 4.8.0?
was (Author: jamestaylor):
Thanks, [~devaraj] & [~prabhjot]. Is it possible that {{User.getCurrent()}}
returns null (in which case we'll need to guard against this in the hashcode
method)? Would be ever want different users to share the same underlying
HConnection? How many different users might be on the same JVM?
[~apurtell] - what do you think?
> 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)
