[
https://issues.apache.org/jira/browse/TAJO-687?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13935006#comment-13935006
]
Tajo QA commented on TAJO-687:
------------------------------
{color:red}*-1 overall.*{color} Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12634712/TAJO-687.patch
against master revision 016b1c6.
{color:green}+1 @author.{color} The patch does not contain any @author
tags.
{color:red}-1 tests included.{color} The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 javac.{color} The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 javadoc.{color} The applied patch does not increase the
total number of javadoc warnings.
{color:green}+1 checkstyle.{color} The patch generated 0 code style errors.
{color:red}-1 findbugs.{color} The patch appears to introduce 183 new
Findbugs (version 1.3.9) warnings.
{color:green}+1 release audit.{color} The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests.{color} The patch passed unit tests in
tajo-catalog/tajo-catalog-server tajo-core/tajo-core-backend.
Test results:
https://builds.apache.org/job/PreCommit-TAJO-Build/216//testReport/
Findbugs warnings:
https://builds.apache.org/job/PreCommit-TAJO-Build/216//artifact/incubator-tajo/patchprocess/newPatchFindbugsWarningstajo-core-backend.html
Console output: https://builds.apache.org/job/PreCommit-TAJO-Build/216//console
This message is automatically generated.
> TajoMaster should pass tajoConf to create catalogServer
> -------------------------------------------------------
>
> Key: TAJO-687
> URL: https://issues.apache.org/jira/browse/TAJO-687
> Project: Tajo
> Issue Type: Bug
> Reporter: DaeMyung Kang
> Assignee: DaeMyung Kang
> Priority: Minor
> Attachments: TAJO-687.patch
>
>
> TajoMaster currently doesn't pass tajoConf to create catalogServer. so it
> create RpcConnectionPool with null tajoConf.
> so it can cause NullPointerException if you use tajo conf in NettyClientBase
--
This message was sent by Atlassian JIRA
(v6.2#6252)
