hive-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Navis (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HIVE-4342) NPE for query involving UNION ALL with nested JOIN and UNION ALL
Date Sun, 21 Apr 2013 04:25:16 GMT

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

Navis updated HIVE-4342:
------------------------

    Status: Patch Available  (was: Open)

[~mihirk] Thanks for reporting this. But generally bug fixes are only for trunk and those
are seldom backported to released versions.
                
> 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
>         Attachments: HIVE-4342.D10407.1.patch, HiveCommands.txt, Query.txt, sourceData1.txt,
sourceData2.txt
>
>
> 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.
> NOTE: you will need to update path to sourceData1.txt and sourceData2.txt in the HiveCommands.txt
to suit your environment.
> 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

Mime
View raw message