[
https://issues.apache.org/jira/browse/HBASE-19301?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16261079#comment-16261079
]
stack commented on HBASE-19301:
-------------------------------
Seeing the patch, createConnection is better than getConnection. +1 on patch.
Let the Phoenix folks know you did this [~anoop.hbase].
On avoiding PB, you'd have to add in bridging code that hard-wires the
Admin/Table Interface up to the server-side RsRpcService and HRegionServer (and
ditto for Master). It'd be really brittle in that any change in the Interface
would need to be re-connected to the Server. It'd be a pain to do especially as
sometimes the Interface method name is not the same as the server-side method
that gets invoked. I'd imagine that it would be worth doing for at least some
call types. I filed HBASE-19316.
> 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)
