[
https://issues.apache.org/jira/browse/HIVE-4342?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mihir Kulkarni updated HIVE-4342:
---------------------------------
Description:
UNION ALL query with JOIN in first part and another UNION ALL in second part
gives NPE.
bq. JOIN
UNION ALL
bq. UNION ALL
Attachments:
1. HiveCommands.txt : command script to setup schema for query under
consideration.
2. sourceData1.txt and sourceData2.txt : required for above command script.
3. Query.txt : Exact query which produces NPE.
Attached files contain the schema and exact query which fails on Hive 0.9.
It is worthwhile to note that the same query executes successfully on Hive 0.7.
was:
UNION ALL query with JOIN in first part and another UNION ALL in second part
gives NPE.
bq. JOIN
UNION ALL
bq. UNION ALL
Attached file (example.txt) contains the schema and exact query which fails on
Hive 0.9.
It is worthwhile to note that the same query executes successfully on Hive 0.7.
> NPE for query involving UNION ALL with nested JOIN and UNION ALL
> ----------------------------------------------------------------
>
> Key: HIVE-4342
> URL: https://issues.apache.org/jira/browse/HIVE-4342
> Project: Hive
> Issue Type: Bug
> Components: Logging, Metastore, Query Processor
> Affects Versions: 0.9.0
> Environment: Red Hat Linux VM with Hive 0.9 and Hadoop 2.0
> Reporter: Mihir Kulkarni
> Assignee: Navis
> Priority: Critical
>
> UNION ALL query with JOIN in first part and another UNION ALL in second part
> gives NPE.
> bq. JOIN
> UNION ALL
> bq. UNION ALL
> Attachments:
> 1. HiveCommands.txt : command script to setup schema for query under
> consideration.
> 2. sourceData1.txt and sourceData2.txt : required for above command script.
> 3. Query.txt : Exact query which produces NPE.
> Attached files contain the schema and exact query which fails on Hive 0.9.
> It is worthwhile to note that the same query executes successfully on Hive
> 0.7.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
