You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@hive.apache.org by "Ashutosh Bapat (JIRA)" <ji...@apache.org> on 2019/01/09 02:39:00 UTC

[jira] [Commented] (HIVE-21108) Assign writeId for stats update for a converted transactional table

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

Ashutosh Bapat commented on HIVE-21108:
---------------------------------------

When we start replicating the stats, the tests for migrated tables fail since there is not writeId associated with the stats update of non-ACID tables on the source. So, we require HIVE-21108 to be fixed before HIVE-21037 is complete.

> Assign writeId for stats update for a converted transactional table
> -------------------------------------------------------------------
>
>                 Key: HIVE-21108
>                 URL: https://issues.apache.org/jira/browse/HIVE-21108
>             Project: Hive
>          Issue Type: Sub-task
>            Reporter: Ashutosh Bapat
>            Assignee: Ashutosh Bapat
>            Priority: Major
>
> When a non-ACID table on the source is converted to an ACID table on the target, the subsequent statistics update (column as well as table level) dumped on the source won't have writeId and snapshot associated with those. When loading those updates on the target we need to associate an appropriate writeId with them. This applies to both a bootstrap and an incremental dump and load.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)