hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alan Gates (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HIVE-18192) Introduce WriteId per table rather than using global transaction id
Date Fri, 01 Dec 2017 18:26:00 GMT

    [ https://issues.apache.org/jira/browse/HIVE-18192?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16274739#comment-16274739
] 

Alan Gates commented on HIVE-18192:
-----------------------------------

Before we go too far down this road, is there a design doc on how this will work?  This will
be a big change to the transaction management system.  In particular it seems like multi-statement
transactions will be affected.  

> Introduce WriteId per table rather than using global transaction id
> -------------------------------------------------------------------
>
>                 Key: HIVE-18192
>                 URL: https://issues.apache.org/jira/browse/HIVE-18192
>             Project: Hive
>          Issue Type: Bug
>          Components: HiveServer2, Transactions
>    Affects Versions: 3.0.0
>            Reporter: anishek
>            Assignee: anishek
>             Fix For: 3.0.0
>
>
> 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 
> <write id, bucketid, rowid>
> a persistable map of global txn id -> to table -> write id for that table has to
be maintained to now allow Snapshot isolation.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message