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 1CAA4200BD5 for ; Thu, 8 Dec 2016 22:08:03 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id 1B3D3160B1F; Thu, 8 Dec 2016 21:08:03 +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 649A6160B0A for ; Thu, 8 Dec 2016 22:08:02 +0100 (CET) Received: (qmail 59113 invoked by uid 500); 8 Dec 2016 21:08:01 -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 59102 invoked by uid 99); 8 Dec 2016 21:08:01 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 08 Dec 2016 21:08:01 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id 3C9DB18BB8D for ; Thu, 8 Dec 2016 21:08:01 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -6.219 X-Spam-Level: X-Spam-Status: No, score=-6.219 tagged_above=-999 required=6.31 tests=[KAM_ASCII_DIVIDERS=0.8, KAM_LAZY_DOMAIN_SECURITY=1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-2.999] autolearn=disabled Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id cZii1UHBEhcD for ; Thu, 8 Dec 2016 21:08:00 +0000 (UTC) Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with SMTP id A8DA35F47A for ; Thu, 8 Dec 2016 21:07:59 +0000 (UTC) Received: (qmail 58660 invoked by uid 99); 8 Dec 2016 21:07:58 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 08 Dec 2016 21:07:58 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id AFAC62C0057 for ; Thu, 8 Dec 2016 21:07:58 +0000 (UTC) Date: Thu, 8 Dec 2016 21:07:58 +0000 (UTC) From: "Andreas Neumann (JIRA)" To: dev@tephra.incubator.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Resolved] (TEPHRA-201) In-progress transactions may become visible when transactions are checkpointed MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Thu, 08 Dec 2016 21:08:03 -0000 [ https://issues.apache.org/jira/browse/TEPHRA-201?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Neumann resolved TEPHRA-201. ------------------------------------ Resolution: Fixed > In-progress transactions may become visible when transactions are checkpointed > ------------------------------------------------------------------------------ > > Key: TEPHRA-201 > URL: https://issues.apache.org/jira/browse/TEPHRA-201 > Project: Tephra > Issue Type: Bug > Components: core > Affects Versions: 0.8.0-incubating, 0.9.0-incubating > Reporter: Poorna Chandra > Assignee: Poorna Chandra > Priority: Blocker > Fix For: 0.10.0-incubating > > > When a transaction is created, the current in-progress list is attached to the transaction object. This list is used to filter out in-progress transactions during read. > The transaction object expects this list to be sorted numerically since it does a binary search for filtering out the in-progress transactions. > When checkpointing feature was added in TEPHRA-96, checkpoints were also added as part of the in-progress list since data writes from checkpoints also have to be filtered out during reads. However adding checkpoints broke the sort order. This leads to binary search not working as expected to filter out in-progress transactions. -- This message was sent by Atlassian JIRA (v6.3.4#6332)