From issues-return-102572-archive-asf-public=cust-asf.ponee.io@hive.apache.org Wed Jan 24 19:20:07 2018 Return-Path: X-Original-To: archive-asf-public@eu.ponee.io Delivered-To: archive-asf-public@eu.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by mx-eu-01.ponee.io (Postfix) with ESMTP id 1A8F618076D for ; Wed, 24 Jan 2018 19:20:07 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id 0B805160C39; Wed, 24 Jan 2018 18:20:07 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 390DA160C4E for ; Wed, 24 Jan 2018 19:20:06 +0100 (CET) Received: (qmail 31513 invoked by uid 500); 24 Jan 2018 18:20:05 -0000 Mailing-List: contact issues-help@hive.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@hive.apache.org Delivered-To: mailing list issues@hive.apache.org Received: (qmail 31466 invoked by uid 99); 24 Jan 2018 18:20:05 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd2-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 24 Jan 2018 18:20:05 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd2-us-west.apache.org (ASF Mail Server at spamd2-us-west.apache.org) with ESMTP id DF24D1A0397 for ; Wed, 24 Jan 2018 18:20:04 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -99.911 X-Spam-Level: X-Spam-Status: No, score=-99.911 tagged_above=-999 required=6.31 tests=[KAM_ASCII_DIVIDERS=0.8, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd2-us-west.apache.org [10.40.0.9]) (amavisd-new, port 10024) with ESMTP id T-OAZ-QXwy5F for ; Wed, 24 Jan 2018 18:20:03 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTP id C38AA5FBA3 for ; Wed, 24 Jan 2018 18:20:02 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id 6117FE25AE for ; Wed, 24 Jan 2018 18:20:01 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 7ACA124112 for ; Wed, 24 Jan 2018 18:20:00 +0000 (UTC) Date: Wed, 24 Jan 2018 18:20:00 +0000 (UTC) From: "Alan Gates (JIRA)" To: issues@hive.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (HIVE-18192) Introduce WriteID per table rather than using global transaction ID MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/HIVE-18192?page=3Dcom.atlassian= .jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D1633= 8020#comment-16338020 ]=20 Alan Gates commented on HIVE-18192: ----------------------------------- I have a question on the design.=C2=A0 I don't understand the MIN_HISTORY_L= EVEL table.=C2=A0 In the doc it says: {quote}=C2=A0need this to ensure that we don=E2=80=99t remove TXNS2WRITE_ID= data before any operation that started while this txn was open/aborted is = still live. This is populated when current_txnid starts and locks in its Va= lidTxnList and the entry is removed when this txn commits/aborts. {quote} Why does this need to be tracked separately?=C2=A0 There is already logic t= o determine when an entry can be removed from TXN_COMPONENTS and COMPLETED_= TXN_COMPONENTS.=C2=A0 Can that not be extended to remove the related entry = from TXNS2WRITE_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 > 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 > > > 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=20 > > which will move to=20 > > For each table modified by the given transaction will have a table level = write ID allocated and a persisted=C2=A0map of global txn id -> to table ->= write id for that table has to be maintained to=C2=A0allow Snapshot isolat= ion. > Readers=C2=A0should use the combination of ValidTxnList and ValidWriteIdL= ist(Table) for snapshot isolation. > =C2=A0 > =C2=A0[Hive Replication - ACID Tables.pdf|https://issues.apache.org/jira/= secure/attachment/12903157/Hive%20Replication-%20ACID%20Tables.pdf] has a s= ection "Per Table Sequences (Write-Id)" with more detials -- This message was sent by Atlassian JIRA (v7.6.3#76005)