[
https://issues.apache.org/jira/browse/HBASE-19301?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16258836#comment-16258836
]
stack commented on HBASE-19301:
-------------------------------
bq. he only disadvantage will be that it will NOT be a short circuit enabled
connection.
A Connection accessing local Server will short-circuit (To be verified).
But perhaps you are referring to difference between an invocation that goes via
protobuf service but skips the rpc invocation vs a direct invocation, one that
skips doing protobuf marshalling/unmarshaling AND rpc?
If this is what you mean, can we make it so there is only one short-circuit
type -- the direct-invocation -- everywhere? I've not looked. Perhaps you have?
i.e. do what the Phoenix 'short-circuit' used do but native inside hbase when
it notices it an invocation against a local server?
Thanks [~anoop.hbase]
> 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
>
>
> 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)
