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] Updated: (HIVE-384) problem in union if the first subquery is a map-only job
Date Sat, 04 Apr 2009 01:34:12 GMT

     [ https://issues.apache.org/jira/browse/HIVE-384?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Namit Jain updated HIVE-384:

    Status: Patch Available  (was: Open)

fixed another minor bug in name of the job which was making my debugging more difficult

> 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
>         Attachments: hive.384.1.patch, hive.384.2.patch, hive.384.3.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