[
https://issues.apache.org/jira/browse/HIVE-19089?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16438992#comment-16438992
]
Sankar Hariappan commented on HIVE-19089:
-----------------------------------------
Patch 07.patch looks good to me!
+1, pending tests.
> Create/Replicate Allocate write-id event
> ----------------------------------------
>
> Key: HIVE-19089
> URL: https://issues.apache.org/jira/browse/HIVE-19089
> 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: ACID, DR, replication
> Fix For: 3.1.0
>
> Attachments: HIVE-19089.01.patch, HIVE-19089.02.patch,
> HIVE-19089.03.patch, HIVE-19089.04.patch, HIVE-19089.05.patch,
> HIVE-19089.06.patch, HIVE-19089.07.patch
>
>
> *EVENT_ALLOCATE_WRITE_ID*
> *Source Warehouse:*
> * Create new event type EVENT_ALLOCATE_WRITE_ID with related message format
> etc.
> * Capture this event when allocate a table write ID from the sequence table
> by ACID operation.
> * Repl dump should read this event from EventNotificationTable and dump the
> message.
> *Target Warehouse:*
> * Repl load should read the event from the dump and get the message.
> * Validate if source txn ID from the event is there in the source-target txn
> ID map. If not there, just noop the event.
> * If valid, then Allocate table write ID from sequence table
> *Extend listener notify event API to add two new parameter , dbconn and
> sqlgenerator to add the events to notification_log table within the same
> transaction*
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
