From dev-return-44094-archive-asf-public=cust-asf.ponee.io@ignite.apache.org Thu Jan 17 15:40:04 2019 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 682FB180663 for ; Thu, 17 Jan 2019 15:40:04 +0100 (CET) Received: (qmail 87196 invoked by uid 500); 17 Jan 2019 14:40:03 -0000 Mailing-List: contact dev-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 dev@ignite.apache.org Received: (qmail 87185 invoked by uid 99); 17 Jan 2019 14:40:03 -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, 17 Jan 2019 14:40:03 +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 F3F0A180C96 for ; Thu, 17 Jan 2019 14:40:02 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-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-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 my14gwrW4dPs for ; Thu, 17 Jan 2019 14:40:01 +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 2CC2F5F4EB for ; Thu, 17 Jan 2019 14:40:01 +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 4F84BE2682 for ; Thu, 17 Jan 2019 14:40:00 +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 13FDA2564E for ; Thu, 17 Jan 2019 14:40:00 +0000 (UTC) Date: Thu, 17 Jan 2019 14:40:00 +0000 (UTC) From: "Ilya Kasnacheev (JIRA)" To: dev@ignite.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Created] (IGNITE-10970) ATOMICITY table creation error message should include TRANSACTIONAL_SNAPSHOT MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 Ilya Kasnacheev created IGNITE-10970: ---------------------------------------- Summary: ATOMICITY table creation error message should include TRANSACTIONAL_SNAPSHOT Key: IGNITE-10970 URL: https://issues.apache.org/jira/browse/IGNITE-10970 Project: Ignite Issue Type: Bug Components: mvcc, sql Affects Versions: 2.7 Reporter: Ilya Kasnacheev {code} 0: jdbc:ignite:thin://localhost> CREATE TABLE city2(id LONG PRIMARY KEY, name VARCHAR,name1 VARCHAR) WITH "atomicity=mvcc"; Error: Invalid value of "ATOMICITY" parameter (should be either TRANSACTIONAL or ATOMIC): mvcc (state=42000,code=1001) {code} This error message should also suggest TRANSACTIONAL_SNAPSHOT to activate MVCC, which totally works. Docs update request sent. -- This message was sent by Atlassian JIRA (v7.6.3#76005)