[
https://issues.apache.org/jira/browse/HADOOP-4139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12630479#action_12630479
]
Hadoop QA commented on HADOOP-4139:
-----------------------------------
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12389888/patch3
against trunk revision 694562.
+1 @author. The patch does not contain any @author tags.
+1 tests included. The patch appears to include 20 new or modified tests.
-1 patch. The patch command could not apply the patch.
Console output:
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/3254/console
This message is automatically generated.
> [Hive] multi group by statement is not optimized
> ------------------------------------------------
>
> Key: HADOOP-4139
> URL: https://issues.apache.org/jira/browse/HADOOP-4139
> Project: Hadoop Core
> Issue Type: Bug
> Components: contrib/hive
> Reporter: Namit Jain
> Assignee: Namit Jain
> Attachments: patch1, patch3
>
>
> A simple multi-group by statement is not optimized. A simple statement like:
> FROM SRC
> INSERT OVERWRITE TABLE DEST1 SELECT SRC.key, count(distinct
> SUBSTR(SRC.value,4)) GROUP BY SRC.key
> INSERT OVERWRITE TABLE DEST2 SELECT SRC.key, count(distinct
> SUBSTR(SRC.value,4)) GROUP BY SRC.key;
> results in making 2 copies of the data (SRC). Instead, the data can be first
> partially aggregated on the distinct value and then aggregated.
> The first step can be common to all group bys.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
