From issues-return-72230-archive-asf-public=cust-asf.ponee.io@ignite.apache.org Thu Aug 16 17:35:05 2018 Return-Path: X-Original-To: archive-asf-public@cust-asf.ponee.io Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by mx-eu-01.ponee.io (Postfix) with SMTP id 863B418076D for ; Thu, 16 Aug 2018 17:35:04 +0200 (CEST) Received: (qmail 14418 invoked by uid 500); 16 Aug 2018 15:35:03 -0000 Mailing-List: contact issues-help@ignite.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@ignite.apache.org Delivered-To: mailing list issues@ignite.apache.org Received: (qmail 14402 invoked by uid 99); 16 Aug 2018 15:35:03 -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; Thu, 16 Aug 2018 15:35:03 +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 4BBE71A1373 for ; Thu, 16 Aug 2018 15:35:03 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -110.301 X-Spam-Level: X-Spam-Status: No, score=-110.301 tagged_above=-999 required=6.31 tests=[ENV_AND_HDR_SPF_MATCH=-0.5, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, USER_IN_DEF_SPF_WL=-7.5, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd2-us-west.apache.org [10.40.0.9]) (amavisd-new, port 10024) with ESMTP id 3bkJK5orMRE2 for ; Thu, 16 Aug 2018 15:35:02 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTP id 371705F534 for ; Thu, 16 Aug 2018 15:35: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 A1673E015E for ; Thu, 16 Aug 2018 15:35: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 E8A40246DB for ; Thu, 16 Aug 2018 15:35:00 +0000 (UTC) Date: Thu, 16 Aug 2018 15:35:00 +0000 (UTC) From: "Vladimir Ozerov (JIRA)" To: issues@ignite.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (IGNITE-3478) Multi-version concurrency control MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/IGNITE-3478?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov updated IGNITE-3478: ------------------------------------ Component/s: (was: mvcc) > Multi-version concurrency control > --------------------------------- > > Key: IGNITE-3478 > URL: https://issues.apache.org/jira/browse/IGNITE-3478 > Project: Ignite > Issue Type: New Feature > Components: cache > Reporter: Alexey Goncharuk > Priority: Major > Labels: important > Fix For: 2.7 > > > Current Ignite SQL does not take into account transaction boundaries. For example, if a transaction atomically changes balance of two accounts, then a concurrent SQL query can see partially committed transaction. This works for data analytics, but does not work for more strict and demanding scenarios. > It would be perfect if we had a mode which ensures transaction boundaries are taken into account for SQL query. -- This message was sent by Atlassian JIRA (v7.6.3#76005)