[
https://issues.apache.org/jira/browse/HBASE-14960?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15058363#comment-15058363
]
Hudson commented on HBASE-14960:
--------------------------------
FAILURE: Integrated in HBase-0.98-on-Hadoop-1.1 #1145 (See
[https://builds.apache.org/job/HBase-0.98-on-Hadoop-1.1/1145/])
HBASE-14960 Fallback to using default RPCControllerFactory if class (apurtell:
rev ee1e453609e7838d8e447bea34b07fa27f11b336)
*
hbase-server/src/test/java/org/apache/hadoop/hbase/client/TestRpcControllerFactory.java
*
hbase-client/src/main/java/org/apache/hadoop/hbase/ipc/RpcControllerFactory.java
> 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)
