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

ASF GitHub Bot commented on HIVE-18192:
---------------------------------------

GitHub user sankarh opened a pull request:

    https://github.com/apache/hive/pull/290

    HIVE-18192: Introduce WriteID per table rather than using global 
transaction ID

    

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/sankarh/hive HIVE-18192

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/hive/pull/290.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #290
    
----
commit ced6d749a7e65c42ed31a8af9e38faaf5941251a
Author: Sankar Hariappan <mailtosankarh@...>
Date:   2018-01-03T05:47:38Z

    HIVE-18192: Introduce WriteID per table rather than using global 
transaction ID

----


> 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, pull-request-available
>             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)

Reply via email to