[
https://issues.apache.org/jira/browse/HBASE-19301?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16263258#comment-16263258
]
Anoop Sam John commented on HBASE-19301:
----------------------------------------
Will give a doc patch and get it in.
bq. You suggesting that ACLs updates get special treatment?
Yes. The grant code is getting executed in the RS where the ACL region sits.
We could directly do writes to region. The ACL grant/revoke ops may not be that
perf critical. So am ok even we continue the current way. And any way that
uses the short circuit connection. But this short circuit connection was
created by hbase super user (starting the server).. Means the runAsLoginUser
is not really working even now also. Already the connection is assigned with
super user so things work. Now if changed to using connection by new API, the
user is the RPC user for whom the CP was running.
So any of the short circuited connection will not work with run as thing as
there is no way to change the user context (As we get the user from the RPC
context. Here no RPC so no rpc context)
> 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)
