[
https://issues.apache.org/jira/browse/HBASE-14960?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15050299#comment-15050299
]
Hadoop QA commented on HBASE-14960:
-----------------------------------
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12776711/hbase-14960_v3.patch
against master branch at commit 9647fee3f0f196d064879afd41b9eff51d5aa036.
ATTACHMENT ID: 12776711
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 3 new
or modified tests.
{color:green}+1 hadoop versions{color}. The patch compiles with all
supported hadoop versions (2.4.0 2.4.1 2.5.0 2.5.1 2.5.2 2.6.0 2.6.1 2.7.0
2.7.1)
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 protoc{color}. The applied patch does not increase the
total number of protoc compiler warnings.
{color:green}+1 javadoc{color}. The javadoc tool did not generate any
warning messages.
{color:green}+1 checkstyle{color}. The applied patch does not generate new
checkstyle errors.
{color:green}+1 findbugs{color}. The patch does not introduce any new
Findbugs (version 2.0.3) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 lineLengths{color}. The patch does not introduce lines
longer than 100
{color:green}+1 site{color}. The mvn post-site goal succeeds with this
patch.
{color:green}+1 core tests{color}. The patch passed unit tests in .
{color:green}+1 zombies{color}. No zombie tests found running at the end of
the build.
Test results:
https://builds.apache.org/job/PreCommit-HBASE-Build/16824//testReport/
Release Findbugs (version 2.0.3) warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/16824//artifact/patchprocess/newFindbugsWarnings.html
Checkstyle Errors:
https://builds.apache.org/job/PreCommit-HBASE-Build/16824//artifact/patchprocess/checkstyle-aggregate.html
Console output:
https://builds.apache.org/job/PreCommit-HBASE-Build/16824//console
This message is automatically generated.
> 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)
