hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vineet Garg (JIRA)" <>
Subject [jira] [Commented] (HIVE-19267) Replicate ACID/MM tables write operations.
Date Sat, 07 Jul 2018 04:01:00 GMT


Vineet Garg commented on HIVE-19267:

The commit pushed to master changes wrong upgrade files (upgrade-2.3.0-to-3.0.0.derby.sql
and upgrade-3.0.0-to-3.1.0.derby.sql). Hive 3.0.0 is already released and 3.1 branch has been
cut off. If this isn't targeted for branch-3 (3.2) then changes should go in upgrade-3.1.0-to-4.0.0.derby.sql
(same for all databases) and hive-schema-3.1 etc shouldn't be touched.

Also please run metastore upgrade/installation tests (you can find more on it at standalone-metastore/DEV-README).
This should tell you if your changes are breaking up-gradation on installation.

BTW is this targeted for 3.2? If so then there are whole new set of files which need to created
and modified.

> Replicate ACID/MM tables write operations.
> ------------------------------------------
>                 Key: HIVE-19267
>                 URL:
>             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
>  * 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

View raw message