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 Chauhan (JIRA)" <ji...@apache.org> on 2018/05/25 06:03:00 UTC

[jira] [Commented] (HIVE-19598) Acid V1 to V2 upgrade

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

Ashutosh Chauhan commented on HIVE-19598:
-----------------------------------------

[~ekoifman] How does it differ from HIVE-19233 ? Seems like this adds a new module and adds UpgradeTool but logic itself looks identical to one in MetaTool. If this is only about packaging change then shall we delete code from MetaTool as well ?

> Acid V1 to V2 upgrade
> ---------------------
>
>                 Key: HIVE-19598
>                 URL: https://issues.apache.org/jira/browse/HIVE-19598
>             Project: Hive
>          Issue Type: Bug
>          Components: Transactions
>    Affects Versions: 3.0.0
>            Reporter: Eugene Koifman
>            Assignee: Eugene Koifman
>            Priority: Critical
>         Attachments: HIVE-19598.02.patch
>
>
> The on-disk layout for full acid (transactional) tables has changed 3.0.
> Any transactional table that has any update/delete events in any deltas that have not been Major compacted, must go through a Major compaction before upgrading to 3.0.  No more update/delete/merge should be run after/during major compaction.
> Not doing so will result in data corruption/loss.
>  
> Need to create a utility tool to help with this process.  HIVE-19233 started this but it needs more work.



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