You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hive.apache.org by "Eugene Koifman (JIRA)" <ji...@apache.org> on 2017/12/20 20:42:00 UTC
[jira] [Comment Edited] (HIVE-18192) Introduce WriteID per table
rather than using global transaction ID
[ https://issues.apache.org/jira/browse/HIVE-18192?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16299027#comment-16299027 ]
Eugene Koifman edited comment on HIVE-18192 at 12/20/17 8:41 PM:
-----------------------------------------------------------------
[~anishek] will share the doc that includes explanation of write ids. Snapshot Isolation will of course be preserved.
was (Author: ekoifman):
I'll try to share the doc by end of the week. Snapshot Isolation will of course be preserved.
> 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: Sub-task
> Components: HiveServer2, Transactions
> Affects Versions: 3.0.0
> Reporter: anishek
> Assignee: Sankar Hariappan
> Labels: ACID, DR
> 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)