hive-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kevin Wilfong (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HIVE-933) Infer bucketing/sorting properties
Date Fri, 09 Nov 2012 05:44:13 GMT

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

Kevin Wilfong commented on HIVE-933:
------------------------------------

If I understand your question correctly, as Namit mentioned in his comment, the metadata for
partitions is what's used, not the table's metadata.
                
> Infer bucketing/sorting properties
> ----------------------------------
>
>                 Key: HIVE-933
>                 URL: https://issues.apache.org/jira/browse/HIVE-933
>             Project: Hive
>          Issue Type: New Feature
>          Components: Query Processor
>            Reporter: Namit Jain
>            Assignee: Kevin Wilfong
>         Attachments: HIVE-933.1.patch.txt, HIVE-933.2.patch.txt
>
>
> This is a long-term plan, and may require major changes.
> From the query, we can figure out the sorting/bucketing properties, and change the metadata
of the destination at that time.
> However, this means that different partitions may have different metadata. Currently,
the query plan is same for all the 
> partitions of the table - we can do the following:
> 1. In the first cut, have a simple approach where you take the union all metadata, and
create the most defensive plan.
> 2. Enhance mapredWork() to include partition specific operator trees.

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