[
https://issues.apache.org/jira/browse/TAJO-772?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13972918#comment-13972918
]
Tajo QA commented on TAJO-772:
------------------------------
{color:red}*-1 overall.*{color} Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12640631/TAJO-772.patch
against master revision 0a76c99.
{color:green}+1 @author.{color} The patch does not contain any @author
tags.
{color:green}+1 tests included.{color} The patch appears to include 14 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 196 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-common tajo-client tajo-core/tajo-core-backend.
Test results:
https://builds.apache.org/job/PreCommit-TAJO-Build/349//testReport/
Findbugs warnings:
https://builds.apache.org/job/PreCommit-TAJO-Build/349//artifact/incubator-tajo/patchprocess/newPatchFindbugsWarningstajo-core-backend.html
Console output: https://builds.apache.org/job/PreCommit-TAJO-Build/349//console
This message is automatically generated.
> TajoDump cannot dump upper/lower mixed case database names.
> -----------------------------------------------------------
>
> Key: TAJO-772
> URL: https://issues.apache.org/jira/browse/TAJO-772
> Project: Tajo
> Issue Type: Bug
> Components: client
> Affects Versions: 0.8, 0.9
> Reporter: Hyunsik Choi
> Assignee: Hyunsik Choi
> Attachments: TAJO-772.patch
>
>
> When users use upper/lower mixed case database names, TajoDump does not work
> correctly. This patch fixes this bug. In addition, this patch adds the unit
> test for TajoDump.
> Additionally, this patch fixes some trivial column resolving bug caused when
> *a column name in target list is not fully qualified* and *another database
> different from the current database of the session* is used in FROM clause.
> Example:
> {code}
> SELECT "LineItem".L_ORDERKEY FROM "TestSelectQuery"."LineItem";
> {code}
--
This message was sent by Atlassian JIRA
(v6.2#6252)
