hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "stack (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-19301) Provide way for CPs to create short circuited connection with custom configurations
Date Mon, 20 Nov 2017 05:52:01 GMT

    [ https://issues.apache.org/jira/browse/HBASE-19301?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16258827#comment-16258827
] 

stack commented on HBASE-19301:
-------------------------------

Thinking about this, do we need to add this to CpEnv [~anoop.hbase]? What is to prevent a
CP from making its own Configuration and subsequently its own Connection? What is advantage
getting it from CpEnv?

> 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)

Mime
View raw message