hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sankar Hariappan (JIRA)" <>
Subject [jira] [Updated] (HIVE-18192) Introduce WriteID per table rather than using global transaction ID
Date Thu, 22 Feb 2018 22:59:00 GMT


Sankar Hariappan updated HIVE-18192:
    Status: Patch Available  (was: Open)

> Introduce WriteID per table rather than using global transaction ID
> -------------------------------------------------------------------
>                 Key: HIVE-18192
>                 URL:
>             Project: Hive
>          Issue Type: Sub-task
>          Components: HiveServer2, Transactions
>    Affects Versions: 3.0.0
>            Reporter: anishek
>            Assignee: Sankar Hariappan
>            Priority: Major
>              Labels: ACID, DR, pull-request-available
>             Fix For: 3.0.0
>         Attachments: HIVE-18192.01.patch, HIVE-18192.02.patch, HIVE-18192.03.patch, HIVE-18192.04.patch,
HIVE-18192.05.patch, HIVE-18192.06.patch, HIVE-18192.07.patch, HIVE-18192.08.patch, HIVE-18192.09.patch,
HIVE-18192.10.patch, HIVE-18192.11.patch, HIVE-18192.12.patch, HIVE-18192.13.patch, HIVE-18192.14.patch,
HIVE-18192.15.patch, HIVE-18192.16.patch
> To support ACID replication, we will be introducing a per table write Id which will replace
the transaction id in the primary key for each row in a ACID table.
> The current primary key is determined via 
>  <original transaction id, bucketid , rowid>
> which will move to 
>  <original write id, bucketid, rowid>
> For each table modified by the given transaction will have a table level write ID allocated
and a persisted map of global txn id -> to table -> write id for that table has to
be maintained to allow Snapshot isolation.
> Readers should use the combination of ValidTxnList and ValidWriteIdList(Table) for snapshot
>  [Hive Replication - ACID Tables.pdf|]
has a section "Per Table Sequences (Write-Id)" with more detials

This message was sent by Atlassian JIRA

View raw message