[
https://issues.apache.org/jira/browse/HBASE-19301?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16279640#comment-16279640
]
stack commented on HBASE-19301:
-------------------------------
To be clear, suggestion:
* Leave getConfiguration in place. Add warnings. Warn that it returns the RS
Connection. Its for light-duty incidental usage ONLY. Pros: Its cache is
populated; it does short-circuit connection. Cons: no heavy-duty usage or will
impinge on RS operation, a close will kill the RS.
* Add to createConnection doc on how to create one that does and that does not
do short-circuiting. Show how to create one on start. Warn about making too
many or will drive up loading on hbase:meta and bloat threads on local RS.
We'd do the above because we are out of time for hbase2. Lets do better in
hbase3. Lets work on the User issues in new JIRA.
> 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-addendum.patch, 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)
