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 AEA68200BDF for ; Sun, 4 Dec 2016 02:16:07 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id A2367160B28; Sun, 4 Dec 2016 01:16: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 E9EAC160B16 for ; Sun, 4 Dec 2016 02:16:06 +0100 (CET) Received: (qmail 44328 invoked by uid 500); 4 Dec 2016 01:16:06 -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 44317 invoked by uid 99); 4 Dec 2016 01:16:06 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd4-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 04 Dec 2016 01:16:06 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd4-us-west.apache.org (ASF Mail Server at spamd4-us-west.apache.org) with ESMTP id B3DF6C03DE for ; Sun, 4 Dec 2016 01:16:05 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd4-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -7.019 X-Spam-Level: X-Spam-Status: No, score=-7.019 tagged_above=-999 required=6.31 tests=[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-us.apache.org ([10.40.0.8]) by localhost (spamd4-us-west.apache.org [10.40.0.11]) (amavisd-new, port 10024) with ESMTP id FJtFbht2Kges for ; Sun, 4 Dec 2016 01:16:04 +0000 (UTC) Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with SMTP id 665145F3F0 for ; Sun, 4 Dec 2016 01:15:59 +0000 (UTC) Received: (qmail 44178 invoked by uid 99); 4 Dec 2016 01:15:58 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 04 Dec 2016 01:15:58 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id 79D872C14F3 for ; Sun, 4 Dec 2016 01:15:58 +0000 (UTC) Date: Sun, 4 Dec 2016 01:15:58 +0000 (UTC) From: "Poorna Chandra (JIRA)" To: dev@tephra.incubator.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Created] (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: Sun, 04 Dec 2016 01:16:07 -0000 Poorna Chandra created TEPHRA-201: ------------------------------------- Summary: 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.9.0-incubating, 0.8.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)