[
https://issues.apache.org/jira/browse/TAJO-829?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13997318#comment-13997318
]
ASF GitHub Bot commented on TAJO-829:
-------------------------------------
GitHub user hyunsik opened a pull request:
https://github.com/apache/tajo/pull/10
TAJO-829: Same constants in groupby clause may cause planning error.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/hyunsik/tajo TAJO-829
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/tajo/pull/10.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #10
----
commit 1c21e8bb692a33530cb804291517f57635b4b091
Author: Hyunsik Choi <[email protected]>
Date: 2014-05-14T06:04:41Z
TAJO-829: Same constants in groupby clause may cause planning error.
----
> Same constants in groupby clause may cause planning error.
> ----------------------------------------------------------
>
> Key: TAJO-829
> URL: https://issues.apache.org/jira/browse/TAJO-829
> Project: Tajo
> Issue Type: Bug
> Components: planner/optimizer
> Reporter: Hyunsik Choi
> Assignee: Hyunsik Choi
> Fix For: 0.9.0, 0.8.1
>
>
> {code}
> select l_partkey as a, '##' as b, '##' as c, count(*) d
> from lineitem
> group by a, b, c
> {code}
> See the above query case. This query causes the planning error. This patch
> fixes the bug. Also, this patch removes duplicated group by keys.
> I verified 'mvn clean install'.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
