hadoop-hive-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Namit Jain (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HIVE-384) problem in union if the first subquery is a map-only job
Date Tue, 07 Apr 2009 00:07:12 GMT

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

Namit Jain commented on HIVE-384:

Zheng pointed out another unrelated bug in the code for explain. The kids of reduce sink was
not made null for all dependent tasks, so only explain plans
of top level tasks were correct.

Although, the reduce sink operator would ignore the kids, so there is no runtime bug

> problem in union if the first subquery is a map-only job
> --------------------------------------------------------
>                 Key: HIVE-384
>                 URL: https://issues.apache.org/jira/browse/HIVE-384
>             Project: Hadoop Hive
>          Issue Type: Bug
>            Reporter: Namit Jain
>            Assignee: Namit Jain
>            Priority: Blocker
>         Attachments: hive.384.1.patch, hive.384.2.patch, hive.384.3.patch, hive.384.4.patch,
> Union needs special handling.
> explain 
>   select unionsrc.key, count(1) FROM (select s2.key as key, s2.value as value from src1
>                                         UNION  ALL  
>                                       select 'tst1' as key, cast(count(1) as string)
as value from src s1) 
>   unionsrc group by unionsrc.key;
> results in a null pointer exception

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message