You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hive.apache.org by "Sankar Hariappan (JIRA)" <ji...@apache.org> on 2018/03/01 08:05:00 UTC

[jira] [Resolved] (HIVE-18720) Replicate Commit Txn operation (without writes)

     [ https://issues.apache.org/jira/browse/HIVE-18720?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Sankar Hariappan resolved HIVE-18720.
-------------------------------------
    Resolution: Duplicate

Closing this as it is duplicate with HIVE-18781. 

> Replicate Commit Txn operation (without writes)
> -----------------------------------------------
>
>                 Key: HIVE-18720
>                 URL: https://issues.apache.org/jira/browse/HIVE-18720
>             Project: Hive
>          Issue Type: Sub-task
>          Components: repl, Transactions
>    Affects Versions: 3.0.0
>            Reporter: mahesh kumar behera
>            Assignee: mahesh kumar behera
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 3.0.0
>
>
> Add new EVENT_COMMIT_TXN to log the metadata/data of all tables/partitions modified within the txn.
> *Source warehouse:*
>  - Create EVENT_COMMIT_TXN event type with corresponding message format etc.
> *Target warehouse:*
>  - Repl load should read this event from the dump.
>  - Validate the source txn ID from the event using the Source-Target Txn ID map maintained in target metastore. Also, need to check if corresponding target txn ID is valid.
>  - If valid, then apply the event and commit the corresponding target transaction.
>  - This new event should be idempotent such that if it is applied twice, then second time it should be loop.
>  *{color:#d04437}{color}* 



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