Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 32F3D200CAE for ; Wed, 17 May 2017 03:17:09 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 318C8160BC1; Wed, 17 May 2017 01:17:09 +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 78E84160BC9 for ; Wed, 17 May 2017 03:17:08 +0200 (CEST) Received: (qmail 88906 invoked by uid 500); 17 May 2017 01:17:07 -0000 Mailing-List: contact dev-help@tephra.incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@tephra.incubator.apache.org Delivered-To: mailing list dev@tephra.incubator.apache.org Received: (qmail 88895 invoked by uid 99); 17 May 2017 01:17:07 -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, 17 May 2017 01:17:07 +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 46B101A04D7 for ; Wed, 17 May 2017 01:17:07 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -99.202 X-Spam-Level: X-Spam-Status: No, score=-99.202 tagged_above=-999 required=6.31 tests=[KAM_ASCII_DIVIDERS=0.8, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, 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 OeXXEVxB_mVr for ; Wed, 17 May 2017 01:17:06 +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 D72C35FDD8 for ; Wed, 17 May 2017 01:17:05 +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 12762E0D8F for ; Wed, 17 May 2017 01:17:05 +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 5D81921946 for ; Wed, 17 May 2017 01:17:04 +0000 (UTC) Date: Wed, 17 May 2017 01:17:04 +0000 (UTC) From: "Poorna Chandra (JIRA)" To: dev@tephra.incubator.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (TEPHRA-138) Improve change set computation for row and column family deletes MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Wed, 17 May 2017 01:17:09 -0000 [ https://issues.apache.org/jira/browse/TEPHRA-138?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Poorna Chandra updated TEPHRA-138: ---------------------------------- Fix Version/s: (was: 0.7.1) > Improve change set computation for row and column family deletes > ---------------------------------------------------------------- > > Key: TEPHRA-138 > URL: https://issues.apache.org/jira/browse/TEPHRA-138 > Project: Tephra > Issue Type: Improvement > Components: hbase-compat-0.96, hbase-compat-0.98, hbase-compat-1.0, tephra-hbase-compat-1.0-cdh, tephra-hbase-compat-1.1 > Reporter: Poorna Chandra > Assignee: Poorna Chandra > > When a row or a column family is deleted, TransactionAwareHTable records the change set at column level instead of just recording the change set at row or column family level. > This does not let us distinguish between cases where a complete row or a column family gets deleted v/s deleting all existing columns of a row or a column family. This leads to ignoring conflicts like the following -- a new column getting added to a row when another transaction with the same row getting deleted is in progress. > Also, the current implementation involves an unnecessary Get call to fetch all columns of a row or a column family on a delete. -- This message was sent by Atlassian JIRA (v6.3.15#6346)