[
https://issues.apache.org/jira/browse/TAJO-682?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13940549#comment-13940549
]
Tajo QA commented on TAJO-682:
------------------------------
{color:red}*-1 overall.*{color} Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12635553/TAJO-682.patch
against master revision 5f7934e.
{color:green}+1 @author.{color} The patch does not contain any @author
tags.
{color:green}+1 tests included.{color} The patch appears to include 1 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: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-core/tajo-core-backend.
Test results:
https://builds.apache.org/job/PreCommit-TAJO-Build/231//testReport/
Findbugs warnings:
https://builds.apache.org/job/PreCommit-TAJO-Build/231//artifact/incubator-tajo/patchprocess/newPatchFindbugsWarningstajo-core-backend.html
Console output: https://builds.apache.org/job/PreCommit-TAJO-Build/231//console
This message is automatically generated.
> RangePartitionAlgorithm should be improved to handle empty texts
> ----------------------------------------------------------------
>
> Key: TAJO-682
> URL: https://issues.apache.org/jira/browse/TAJO-682
> Project: Tajo
> Issue Type: Bug
> Components: distributed query plan
> Affects Versions: 0.8-incubating
> Reporter: Jihoon Son
> Labels: patch
> Fix For: 0.8-incubating
>
> Attachments: TAJO-682.patch
>
>
> See the title.
> When one of input datums is an empty TextDatum,
> java.lang.StringIndexOutOfBoundsException occurs because, currently, the
> first characters of both input datum are always compared to calculate the
> cardinality.
--
This message was sent by Atlassian JIRA
(v6.2#6252)