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

Mark Wagner commented on HIVE-5302:
-----------------------------------

Yes, that's right [~appodictic]. This ultimately traces back to the changes 
made in HIVE-3833.

[~busbey], I'm having difficulty reproducing the failure. I've added your 
changes to avro_partitioned, as well as a select from the table. It goes 
through cleanly and the result looks correct:
{noformat}
An Unearthly Child      23 November 1963        1
The Power of the Daleks 5 November 1966 2
Horror of Fang Rock     3 September 1977        4
Castrolava      4 January 1982  5
The Mysterious Planet   6 September 1986        6
{noformat}

I ran this on trunk and pulled right before running. Any idea what might be 
different between us? How did the test case fail for you without the 
MetaStoreUtils changes?
                
> PartitionPruner fails on Avro non-partitioned data
> --------------------------------------------------
>
>                 Key: HIVE-5302
>                 URL: https://issues.apache.org/jira/browse/HIVE-5302
>             Project: Hive
>          Issue Type: Bug
>          Components: Serializers/Deserializers
>    Affects Versions: 0.11.0
>            Reporter: Sean Busbey
>            Assignee: Sean Busbey
>            Priority: Blocker
>              Labels: avro
>         Attachments: HIVE-5302.1-branch-0.12.patch.txt, 
> HIVE-5302.1.patch.txt, HIVE-5302.1.patch.txt
>
>
> While updating HIVE-3585 I found a test case that causes the failure in the 
> MetaStoreUtils partition retrieval from back in HIVE-4789.
> in this case, the failure is triggered when the partition pruner is handed a 
> non-partitioned table and has to construct a pseudo-partition.
> e.g.
> {code}
>   INSERT OVERWRITE TABLE partitioned_table PARTITION(col) SELECT id, foo, col 
> FROM non_partitioned_table WHERE col <= 9;
> {code}

--
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

Reply via email to