From issues-return-55630-archive-asf-public=cust-asf.ponee.io@ignite.apache.org Fri Jan 19 10:13:07 2018 Return-Path: X-Original-To: archive-asf-public@eu.ponee.io Delivered-To: archive-asf-public@eu.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by mx-eu-01.ponee.io (Postfix) with ESMTP id A69D2180607 for ; Fri, 19 Jan 2018 10:13:07 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id 957B1160C28; Fri, 19 Jan 2018 09:13: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 DA32D160C27 for ; Fri, 19 Jan 2018 10:13:06 +0100 (CET) Received: (qmail 62369 invoked by uid 500); 19 Jan 2018 09:13:06 -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 62360 invoked by uid 99); 19 Jan 2018 09:13:06 -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; Fri, 19 Jan 2018 09:13:06 +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 90EB61805D6 for ; Fri, 19 Jan 2018 09:13:05 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -107.911 X-Spam-Level: X-Spam-Status: No, score=-107.911 tagged_above=-999 required=6.31 tests=[ENV_AND_HDR_SPF_MATCH=-0.5, KAM_ASCII_DIVIDERS=0.8, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, 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 CtHg8GdXLPwT for ; Fri, 19 Jan 2018 09:13:04 +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 B42FD5FB37 for ; Fri, 19 Jan 2018 09:13:03 +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 EC79AE095C for ; Fri, 19 Jan 2018 09:13:02 +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 81036241C4 for ; Fri, 19 Jan 2018 09:13:01 +0000 (UTC) Date: Fri, 19 Jan 2018 09:13:01 +0000 (UTC) From: "Vladimir Ozerov (JIRA)" To: issues@ignite.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (IGNITE-7248) "Schema not found" error when setting streaming mode for JDBC driver 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-7248?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov updated IGNITE-7248: ------------------------------------ Component/s: jdbc > "Schema not found" error when setting streaming mode for JDBC driver > -------------------------------------------------------------------- > > Key: IGNITE-7248 > URL: https://issues.apache.org/jira/browse/IGNITE-7248 > Project: Ignite > Issue Type: Bug > Components: jdbc > Affects Versions: 2.3 > Reporter: Alexey Kukushkin > Assignee: Vladimir Ozerov > Priority: Major > Fix For: 2.4 > > > Using JDBC "thick" driver in streaming mode fails with a "Schema not found" erorr: > {code} > Connection connection = DriverManager.getConnection("jdbc:ignite:cfg://streaming=true:cache=CACHE@file:/path-to-ignite-config.xml"); > {code} > using connection to create a table works fine but this exception is generated when using the connection to execute INSER INTO... > {code} > class org.apache.ignite.internal.processors.query.IgniteSQLException: Failed > to set schema for DB connection for thread [schema=] > org.h2.jdbc.JdbcSQLException: Schema not found; SQL statement: > SET SCHEMA "" [90079-195] > {code} > See [User List|http://apache-ignite-users.70518.x6.nabble.com/Cannot-insert-data-into-table-using-JDBC-tc17477.html] for more details -- This message was sent by Atlassian JIRA (v7.6.3#76005)