[
https://issues.apache.org/jira/browse/TAJO-718?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13949217#comment-13949217
]
Tajo QA commented on TAJO-718:
------------------------------
{color:red}*-1 overall.*{color} Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12637129/TAJO-718.patch
against master revision 9d00f9f.
{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: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-core/tajo-core-backend.
Test results:
https://builds.apache.org/job/PreCommit-TAJO-Build/271//testReport/
Findbugs warnings:
https://builds.apache.org/job/PreCommit-TAJO-Build/271//artifact/incubator-tajo/patchprocess/newPatchFindbugsWarningstajo-core-backend.html
Console output: https://builds.apache.org/job/PreCommit-TAJO-Build/271//console
This message is automatically generated.
> A group-by clause with the same columns but aliased causes planning error.
> --------------------------------------------------------------------------
>
> Key: TAJO-718
> URL: https://issues.apache.org/jira/browse/TAJO-718
> Project: Tajo
> Issue Type: Bug
> Components: planner/optimizer
> Affects Versions: 0.8-incubating, 1.0-incubating
> Reporter: Hyunsik Choi
> Assignee: Hyunsik Choi
> Attachments: TAJO-718.patch
>
>
> The reproduction SQL statement is as follows:
> {code}
> SELECT
> "lineitem".l_orderkey AS l_orderkey,
> "lineitem".l_orderkey AS l_orderkey1,
> COUNT ("lineitem".l_orderkey) AS T57801e5322bc50
> FROM
> "lineitem"
> GROUP BY
> l_orderkey, l_orderkey1
> ORDER BY
> l_orderkey, l_orderkey1;
> {code}
--
This message was sent by Atlassian JIRA
(v6.2#6252)
