[jira] [Commented] (HIVE-3529) Incorrect partition bucket/sort metadata when overwriting partition with different metadata from table

["Kevin Wilfong (JIRA)" <ji...@apache.org>]

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

Kevin Wilfong commented on HIVE-3529:
-------------------------------------

My proposed fix is to by default always overwrite the partition's bucket/sorting metadata with that of the table when overwriting a table.  My main motivation for doing this vs. using the partition's metadata is dynamic partitions.  The potential for having to manage maintaining all the different bucket/sorting schemes across several partitions which are overwritten dynamically sounds like a new feature rather than a bug fix, and could be done in a separate JIRA.
                
> Incorrect partition bucket/sort metadata when overwriting partition with different metadata from table
> ------------------------------------------------------------------------------------------------------
>
>                 Key: HIVE-3529
>                 URL: https://issues.apache.org/jira/browse/HIVE-3529
>             Project: Hive
>          Issue Type: Bug
>          Components: Query Processor
>    Affects Versions: 0.10.0
>            Reporter: Kevin Wilfong
>            Assignee: Kevin Wilfong
>
> If you have a partition with bucket/sort metadata set, then you alter the table to have different bucket/sort metadata, and insert overwrite the partition with hive.enforce.bucketing=true and/or hive.enforce.sorting=true, the partition data will be bucketed/sorted by the table's metadata, but the partition will have the same metadata.
> This could result in wrong results.

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