[
https://issues.apache.org/jira/browse/HBASE-19301?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anoop Sam John updated HBASE-19301:
-----------------------------------
Resolution: Fixed
Hadoop Flags: Reviewed
Release Note:
Provided a way for the CP users to create a short circuitable connection with
custom configs.
createConnection(Configuration) is added to MasterCoprocessorEnvironment,
RegionServerCoprocessorEnvironment and RegionCoprocessorEnvironment.
The getConnection() version available in these Env interfaces return a single
cluster connection created at the server (which server also uses) where as this
new method will create new connection. The difference from connection created
at client side (using ConnectionFactory APIs) is that this connection can short
circuit the calls to same server avoiding the RPC paths. The connection will
NOT be cached/maintained by server. That should be done the CPs.
Status: Resolved (was: Patch Available)
> 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)
