[
https://issues.apache.org/jira/browse/HIVE-19267?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16535630#comment-16535630
]
Sankar Hariappan edited comment on HIVE-19267 at 7/7/18 5:17 AM:
-----------------------------------------------------------------
[~maheshk114],
I think, [~vgarg]'s point is, if this patch is targeted to branch-3 (3.2.0),
then need to create upgrade-3.1.0-to-3.2.0.xxxx.sql scripts for each RDBMS and
move all the changes relevant to this patch from
upgrade-3.0.0-to-3.1.0.xxxx.sql. Also, as 3.1.0 is already cut-off, we need to
keep these changes in hive-schema-3.2.0.xxxx.sql scripts and remove from
hive-schema-3.1.0.xxxx.sql.
was (Author: sankarh):
[~maheshk114],
I think, [~vgarg]'s point is, if this patch is targeted to branch-3 (3.2.0),
then need to create upgrade-3.1.0-to-3.2.0.xxxx.sql scripts for each RDBMS and
move all the changes from upgrade-3.0.0-to-3.1.0.xxxx.sql. Also, as 3.1.0 is
already cut-off, we need to keep these changes in hive-schema-3.2.0.xxxx.sql
scripts and remove from hive-schema-3.1.0.xxxx.sql.
> Replicate ACID/MM tables write operations.
> ------------------------------------------
>
> Key: HIVE-19267
> URL: https://issues.apache.org/jira/browse/HIVE-19267
> 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, pull-request-available, replication
> Fix For: 4.0.0
>
> Attachments: HIVE-19267.01-branch-3.patch, HIVE-19267.01.patch,
> HIVE-19267.02.patch, HIVE-19267.03.patch, HIVE-19267.04.patch,
> HIVE-19267.05.patch, HIVE-19267.06.patch, HIVE-19267.07.patch,
> HIVE-19267.08.patch, HIVE-19267.09.patch, HIVE-19267.10.patch,
> HIVE-19267.11.patch, HIVE-19267.12.patch, HIVE-19267.13.patch,
> HIVE-19267.14.patch, HIVE-19267.15.patch, HIVE-19267.16.patch,
> HIVE-19267.17.patch, HIVE-19267.18.patch, HIVE-19267.19.patch,
> HIVE-19267.20.patch, HIVE-19267.21.patch, HIVE-19267.22.patch
>
>
>
> h1. Replicate ACID write Events
> * Create new EVENT_WRITE event with related message format to log the write
> operations with in a txn along with data associated.
> * Log this event when perform any writes (insert into, insert overwrite,
> load table, delete, update, merge, truncate) on table/partition.
> * If a single MERGE/UPDATE/INSERT/DELETE statement operates on multiple
> partitions, then need to log one event per partition.
> * DbNotificationListener should log this type of event to special metastore
> table named "MTxnWriteNotificationLog".
> * This table should maintain a map of txn ID against list of
> tables/partitions written by given txn.
> * The entry for a given txn should be removed by the cleaner thread that
> removes the expired events from EventNotificationTable.
> h1. Replicate Commit Txn operation (with writes)
> Add new EVENT_COMMIT_TXN to log the metadata/data of all tables/partitions
> modified within the txn.
> *Source warehouse:*
> * This event should read the EVENT_WRITEs from "MTxnWriteNotificationLog"
> metastore table to consolidate the list of tables/partitions modified within
> this txn scope.
> * Based on the list of tables/partitions modified and table Write ID, need
> to compute the list of delta files added by this txn.
> * Repl dump should read this message and dump the metadata and delta files
> list.
> *Target warehouse:*
> * Ensure snapshot isolation at target for on-going read txns which shouldn't
> view the data replicated from committed txn. (Ensured with open and allocate
> write ID events).
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
