From dev-return-42591-archive-asf-public=cust-asf.ponee.io@ignite.apache.org Wed Nov 28 21:12:13 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 A4EA9180658 for ; Wed, 28 Nov 2018 21:12:12 +0100 (CET) Received: (qmail 40730 invoked by uid 500); 28 Nov 2018 20:12:11 -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 40712 invoked by uid 99); 28 Nov 2018 20:12:11 -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; Wed, 28 Nov 2018 20:12:11 +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 AA8031806A2 for ; Wed, 28 Nov 2018 20:12:10 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 1.998 X-Spam-Level: * X-Spam-Status: No, score=1.998 tagged_above=-999 required=6.31 tests=[DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=2, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=disabled Authentication-Results: spamd3-us-west.apache.org (amavisd-new); dkim=pass (2048-bit key) header.d=gridgain-com.20150623.gappssmtp.com 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 6snEDgJWOulH for ; Wed, 28 Nov 2018 20:12:08 +0000 (UTC) Received: from mail-ua1-f53.google.com (mail-ua1-f53.google.com [209.85.222.53]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTPS id DD9E760F84 for ; Wed, 28 Nov 2018 20:12:07 +0000 (UTC) Received: by mail-ua1-f53.google.com with SMTP id j3so9393642uap.3 for ; Wed, 28 Nov 2018 12:12:07 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gridgain-com.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=e4qULn2o4bG8LRhwS8VGqTorejUnI2a/gjTe10urQjQ=; b=Vf8/dE4gJaOBytutGGUoO3XLLdSc3Gq5P7igr5JXHxRGFsveUsUYqJrsE2ZBkacRDr Bmc8i0Er/r7n8evbF6hULcAnxs5IMHnc1n8j7tCr0Rfmfr+YD9VCcJOiTqUA9/1YXnYc 3OrfheRTAY3YeX36s8I+y+g7snT3CVdTbUf4W45e9v63kuemDaBgF/k6N/ibGhDoOw4c dFbN+61WcBW7+2TaTY6TATUH3IbBtkumbK36E2mi6sIqTZ1H/Xyijs3lwM/MDy1TTF6/ WxXFlK82ghcQABMJhoJ6WDT2GKSmVMHS2yfcetrUspB/6rAhAUeBgVUzDOqSi4JczLmT XKQg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=e4qULn2o4bG8LRhwS8VGqTorejUnI2a/gjTe10urQjQ=; b=oSeMko/6j0nFeQswp1c4V/32aAXSaEdao6h3PflJkd4hlFx8bdFF0uqqRXUjezv1+F KrwRRqIC2NX5lceiq9xD8vZQnZCjY9mgMzCsIHfTFvub2P01TnWDGyM63naZoy7FUg+a 5I8MlYPySC6SyJruFvhVWdV5lSONik7Nza0m8gP4lGVQp7pWbK4eLchXwmhuBTbCXQ22 IHJNo4mM+I6vPknRvb72ANsT4zfkvzL7cyJC3ZayfULCXZDfyNVrnctoVqu37w0Wu7NF U5c0NYIP1Oh0GOHxqSvroWyhtwGLTIrd+T9r/al4sSENckwYre51RlLyxIB9jXIai5qN xf7A== X-Gm-Message-State: AA+aEWanDXJNNozHpsICmRsfrfziUeMswKLLywcDRvuY7xBWlJUcRiUw l9ZWbX3GAsIIwA3iFy7ocAdnt9+Sd94WHIMOBsfISorV X-Google-Smtp-Source: AFSGD/Vp9wOYpFM6TAtAQon+5XL+7Qu7H16bwQt/hK+hrnOArgLk9wSZj116blsnw6PgakyN7GUmvncTHTFkvzBDJVg= X-Received: by 2002:a9f:300d:: with SMTP id h13mr16462393uab.80.1543435920496; Wed, 28 Nov 2018 12:12:00 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: From: Vladimir Ozerov Date: Wed, 28 Nov 2018 23:11:50 +0300 Message-ID: Subject: Re: Case sensitive indexes question. To: dev Content-Type: multipart/alternative; boundary="000000000000c6897f057bbf2d64" --000000000000c6897f057bbf2d64 Content-Type: text/plain; charset="UTF-8" Hi Zhenya, Answering your questions: 1) Yes, this is expected 2) This is standard rule applicable for almost all vendors and all SQL commands - object name without quotes is normalized to some case (upper or lower), object name in qoutes is left as is 3) Hard to say, need to experiment with it 4) We don't Some vendors allow it (MySQL, Postgres), may be some other's don't. We cannot restrict their usage in AI 2.x as it may break existing applications. Neither I think we should restrict it - nothing is broken. IMO what we do need is to inform user that he is doing something strange and let him decide what to do. This could be a warning in the log, special "performance suggestions" SQL view, whatever. Vladimir. On Wed, Nov 28, 2018 at 8:57 PM Zhenya wrote: > Igniters, i found that ignite allow to create multiple case sensitive > indexes with equal fields collection, i.e. no exception and warn here: > > CREATE INDEX \"title_idx\" ON books (title); > CREATE INDEX \"tiTLE_IDX\" ON books (title); > > 1. in this case will be created two different index structures. > 2. documentation [1] not clarify that quotation usage will create > different ones and quotation absence will create index name in upper > registry. > 3. what index, query planner would be use? > 4. and main question: why do we need this functional? > > i found that other vendors not allow such indexes [2] > > if we can`t change this in 2.x version due to some backward compatibility > reasons, plz show them, i have no clue why we can`t change it in near > release versions. > > [1] https://apacheignite-sql.readme.io/docs/create-index > [2] > > https://oracle-base.com/articles/12c/multiple-indexes-on-same-set-of-columns-12cr1 > > thanks! > --000000000000c6897f057bbf2d64--