[ 
https://issues.apache.org/jira/browse/HIVE-2750?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13193949#comment-13193949
 ] 

Hudson commented on HIVE-2750:
------------------------------

Integrated in Hive-trunk-h0.21 #1222 (See 
[https://builds.apache.org/job/Hive-trunk-h0.21/1222/])
    HIVE-2750 Hive multi group by single reducer optimization causes invalid 
column
reference error (Kevin Wilfong via namit)

namit : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1236150
Files : 
* /hive/trunk/ql/src/java/org/apache/hadoop/hive/ql/parse/SemanticAnalyzer.java
* /hive/trunk/ql/src/test/queries/clientpositive/groupby_multi_single_reducer2.q
* 
/hive/trunk/ql/src/test/results/clientpositive/groupby_multi_single_reducer2.q.out

                
> Hive multi group by single reducer optimization causes invalid column 
> reference error
> -------------------------------------------------------------------------------------
>
>                 Key: HIVE-2750
>                 URL: https://issues.apache.org/jira/browse/HIVE-2750
>             Project: Hive
>          Issue Type: Bug
>            Reporter: Kevin Wilfong
>            Assignee: Kevin Wilfong
>         Attachments: HIVE-2750.D1455.1.patch
>
>
> After the optimization, if two query blocks have the same distinct clause and 
> the same group by keys, but the first query block does not reference all the 
> rows the second query block does, an invalid column reference error is raised 
> for the columns unreferenced in the first query block.
> E.g.
> FROM src
> INSERT OVERWRITE TABLE dest_g2 SELECT substr(src.key,1,1), count(DISTINCT 
> src.key) WHERE substr(src.key,1,1) >= 5 GROUP BY substr(src.key,1,1)
> INSERT OVERWRITE TABLE dest_g3 SELECT substr(src.key,1,1), count(DISTINCT 
> src.key), count(src.value) WHERE substr(src.key,1,1) < 5 GROUP BY 
> substr(src.key,1,1);
> This results in an invalid column reference error on src.value

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to