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

Anoop Sam John commented on HBASE-19301:
----------------------------------------

Good points.  The created connection having the same user (the one context 
which created it) is what we really need I believe. This is ok. Ya we should 
doc it clearly may be.  The case is that as the RPC is short circuited, the run 
as any other user thing wont work out.  
No need to provide extra API for creation of non short circuited connection. CP 
users can use ConnectionFactory methods any way.
So as part of closing this issue, some extra doc is what we need. Ok Stack?

So we can not really short circuit the put to ACL region (in grant, revoke 
etc).  If we have concerns over those writes happening via RPC, we should 
directly put to region. Any way the grant is an EP call and that works on a 
region where the row has to go in.  We can get the region from CPEnv now. Stack 
WDYT?

> Provide way for CPs to create short circuited connection with custom 
> configurations
> -----------------------------------------------------------------------------------
>
>                 Key: HBASE-19301
>                 URL: https://issues.apache.org/jira/browse/HBASE-19301
>             Project: HBase
>          Issue Type: Sub-task
>          Components: Coprocessors
>            Reporter: Anoop Sam John
>            Assignee: Anoop Sam John
>             Fix For: 2.0.0-beta-1
>
>         Attachments: HBASE-19301.patch, HBASE-19301_V2.patch, 
> HBASE-19301_V2.patch
>
>
> Over in HBASE-18359 we have discussions for this.
> Right now HBase provide getConnection() in RegionCPEnv, MasterCPEnv etc. But 
> this returns a pre created connection (per server).  This uses the configs at 
> hbase-site.xml at that server. 
> Phoenix needs creating connection in CP with some custom configs. Having this 
> custom changes in hbase-site.xml is harmful as that will affect all 
> connections been created at that server.
> This issue is for providing an overloaded getConnection(Configuration) API



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Reply via email to