[jira] [Commented] (HBASE-14960) Fallback to using default RPCControllerFactory if class cannot be loaded

["Vsevolod Ostapenko (JIRA)" <ji...@apache.org>]

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

Vsevolod Ostapenko commented on HBASE-14960:
--------------------------------------------

Hortonworks still ships HBase 1.1.2 in the most recent HDP 2.5 releases. Is it possible to have a patch for this issue on 1.1.2?

> Fallback to using default RPCControllerFactory if class cannot be loaded
> ------------------------------------------------------------------------
>
>                 Key: HBASE-14960
>                 URL: https://issues.apache.org/jira/browse/HBASE-14960
>             Project: HBase
>          Issue Type: Bug
>            Reporter: Enis Soztutar
>            Assignee: Enis Soztutar
>             Fix For: 2.0.0, 1.2.0, 1.3.0, 0.98.17
>
>         Attachments: HBASE-14960-0.98.patch, hbase-14960_v1.patch, hbase-14960_v2.patch, hbase-14960_v3.patch, hbase-14960_v4.patch
>
>
> In Phoenix + HBase clusters, the hbase-site.xml configuration will point to a custom rpc controller factory which is a Phoenix-specific one to configure the priorities for index and system catalog table. 
> However, sometimes these Phoenix-enabled clusters are used from pure-HBase client applications resulting in ClassNotFoundExceptions in application code or MapReduce jobs. Since hbase configuration is shared between Phoenix-clients and HBase clients, having different configurations at the client side is hard. 
> We can instead try to load up the RPCControllerFactory from conf, and if not found, fallback to the default one (in case this is a pure HBase client). In case Phoenix is already in the classpath, it will work as usual. 
> This does not affect the rpc scheduler factory since it is only used at the server side. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)