[
https://issues.apache.org/jira/browse/HIVE-384?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zheng Shao updated HIVE-384:
----------------------------
Resolution: Fixed
Fix Version/s: 0.4.0
0.3.1
Release Note: HIVE-384. Fixing UNION ALL when the first job is a map-only
job. (Namit Jain via zshao)
Hadoop Flags: [Reviewed]
Status: Resolved (was: Patch Available)
Thanks Namit.
> 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
> Fix For: 0.3.1, 0.4.0
>
> Attachments: hive.384.1.patch, hive.384.2.patch, hive.384.3.patch,
> hive.384.4.patch, hive.384.5.patch, hive.384.6.patch
>
>
> Union needs special handling.
> explain
> select unionsrc.key, count(1) FROM (select s2.key as key, s2.value as value
> from src1 s2
> 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.
