[
https://issues.apache.org/jira/browse/HBASE-14960?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15050128#comment-15050128
]
stack commented on HBASE-14960:
-------------------------------
bq. Thanks Enis. +1(non-binding)
[~ashish singhi] No such thing as a non-binding review +1, FYI. Your +1 is
effectively same as anyone elses... (give or take quality of review...)
> 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
>
> Attachments: hbase-14960_v1.patch, hbase-14960_v2.patch,
> hbase-14960_v3.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)
