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

Nicholas Brenwald commented on HIVE-11410:
------------------------------------------

[~mmccline] I have done some further testing today compiling from source 
various branches. 

The issue only seems to be present in release-1.1.0 (which is part of the 
Cloudera distribution we use). The issue cannot be reproduced in branch-1.1 or 
branch-1.2 (even when using our environment variables/hive-site.xml etc). As 
such I think this can be marked as resolved. 
Thanks for looking into this and sorry for the false alarm.

> Join with subquery containing a group by incorrectly returns no results
> -----------------------------------------------------------------------
>
>                 Key: HIVE-11410
>                 URL: https://issues.apache.org/jira/browse/HIVE-11410
>             Project: Hive
>          Issue Type: Bug
>          Components: Hive
>    Affects Versions: 1.1.0
>            Reporter: Nicholas Brenwald
>            Assignee: Matt McCline
>            Priority: Minor
>         Attachments: hive-site.xml
>
>
> Start by creating a table *t* with columns *c1* and *c2* and populate with 1 
> row of data. For example create table *t* from an existing table which 
> contains at least 1 row of data by running:
> {code}
> create table t as select 'abc' as c1, 0 as c2 from Y limit 1; 
> {code}
> Table *t* looks like the following:
> ||c1||c2||
> |abc|0|
> Running the following query then returns zero results.
> {code}
> SELECT 
>   t1.c1
> FROM 
>   t t1
> JOIN
> (SELECT 
>    t2.c1,
>    MAX(t2.c2) AS c2
>  FROM 
>    t t2 
>  GROUP BY 
>    t2.c1
> ) t3
> ON t1.c2=t3.c2
> {code}
> However, we expected to see the following:
> ||c1||
> |abc|
> The problem seems to relate to the fact that in the subquery, we group by 
> column *c1*, but this is not subsequently used in the join condition.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to