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

Tajo QA commented on TAJO-1583:
-------------------------------

{color:green}*+1 overall.*{color}  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12729040/TAJO-1583.patch
  against master revision release-0.9.0-rc0-279-g9540f16.

    {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 test files.

    {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: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 core tests.{color}  The patch passed unit tests in 
tajo-catalog/tajo-catalog-client tajo-catalog/tajo-catalog-server tajo-client 
tajo-core tajo-rpc/tajo-rpc-protobuf.

Test results: 
https://builds.apache.org/job/PreCommit-TAJO-Build/764//testReport/
Console output: https://builds.apache.org/job/PreCommit-TAJO-Build/764//console

This message is automatically generated.

> Remove ServerCallable in RPC client
> -----------------------------------
>
>                 Key: TAJO-1583
>                 URL: https://issues.apache.org/jira/browse/TAJO-1583
>             Project: Tajo
>          Issue Type: Task
>          Components: client
>            Reporter: Jinho Kim
>            Assignee: Jinho Kim
>            Priority: Minor
>         Attachments: TAJO-1583.patch
>
>
> TAJO-1563 contains retry during invocation internally.
> We should remove it for more clearly. because it invoke repeatedly without 
> reference to an application error



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

Reply via email to