From issues-return-89302-archive-asf-public=cust-asf.ponee.io@ignite.apache.org Fri Jan 25 14:07:03 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 571F1180608 for ; Fri, 25 Jan 2019 14:07:03 +0100 (CET) Received: (qmail 81944 invoked by uid 500); 25 Jan 2019 13:07:02 -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 81935 invoked by uid 99); 25 Jan 2019 13:07:02 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd1-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 25 Jan 2019 13:07:02 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd1-us-west.apache.org (ASF Mail Server at spamd1-us-west.apache.org) with ESMTP id 22810C77AE for ; Fri, 25 Jan 2019 13:07:02 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-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 (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id w6eDsFeGRXJu for ; Fri, 25 Jan 2019 13:07:01 +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 EBA095FD5D for ; Fri, 25 Jan 2019 13:07:00 +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 820CDE006D for ; Fri, 25 Jan 2019 13:07: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 3CF8F242F1 for ; Fri, 25 Jan 2019 13:07:00 +0000 (UTC) Date: Fri, 25 Jan 2019 13:07:00 +0000 (UTC) From: "Vladimir Ozerov (JIRA)" To: issues@ignite.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Assigned] (IGNITE-7743) JDBC driver allows to connect to non existent schema MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/IGNITE-7743?page=3Dcom.atlassi= an.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov reassigned IGNITE-7743: --------------------------------------- Assignee: (was: Pavel Kuznetsov) > JDBC driver allows to connect to non existent schema > ---------------------------------------------------- > > Key: IGNITE-7743 > URL: https://issues.apache.org/jira/browse/IGNITE-7743 > Project: Ignite > Issue Type: Bug > Components: jdbc, sql > Affects Versions: 2.3 > Reporter: Valentin Kulichenko > Priority: Major > Labels: usability > > Currently, if=C2=A0one=C2=A0creates a cache without DDL (via {{QueryEntit= y}} or {{indexedTypes}}), separate schema for this cache is created. Schema= name is case sensitive, so to connect to it with JDBC driver, it's require= d to provide the name in quotes. Here is how it looks like in SqlLine: > {noformat} > ./bin/sqlline.sh -u jdbc:ignite:thin://127.0.0.1/\"CacheQueryExamplePerso= ns\" > {noformat} > However, if name is provided without quotes, driver still connects, but t= hen fails with a very unclear exception when a query is executed: > {noformat} > ./bin/sqlline.sh -u jdbc:ignite:thin://127.0.0.1/CacheQueryExamplePersons= {noformat} > This is a huge usability issue. We should disallow connections to schema = that does not exist, throw exception in this case. Exception should provide= proper explanation how to connect properly. -- This message was sent by Atlassian JIRA (v7.6.3#76005)