Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 02B58200CC1 for ; Mon, 10 Jul 2017 12:38:52 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 01007166A9B; Mon, 10 Jul 2017 10:38:52 +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 50BDB166A79 for ; Mon, 10 Jul 2017 12:38:51 +0200 (CEST) Received: (qmail 82245 invoked by uid 500); 10 Jul 2017 10:38:50 -0000 Mailing-List: contact issues-help@drill.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@drill.apache.org Delivered-To: mailing list issues@drill.apache.org Received: (qmail 82235 invoked by uid 99); 10 Jul 2017 10:38:50 -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; Mon, 10 Jul 2017 10:38:50 +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 E7E4D1928D6 for ; Mon, 10 Jul 2017 10:38:49 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -99.202 X-Spam-Level: X-Spam-Status: No, score=-99.202 tagged_above=-999 required=6.31 tests=[KAM_ASCII_DIVIDERS=0.8, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id 330RZ_07EbZQ for ; Mon, 10 Jul 2017 10:38:49 +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 DE54C62610 for ; Mon, 10 Jul 2017 10:30:04 +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 6C89CE0984 for ; Mon, 10 Jul 2017 10:30:03 +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 7B41E24696 for ; Mon, 10 Jul 2017 10:30:01 +0000 (UTC) Date: Mon, 10 Jul 2017 10:30:01 +0000 (UTC) From: "Arina Ielchiieva (JIRA)" To: issues@drill.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (DRILL-4264) Dots in identifier are not escaped correctly MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Mon, 10 Jul 2017 10:38:52 -0000 [ https://issues.apache.org/jira/browse/DRILL-4264?page=3Dcom.atlassian= .jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D1608= 0129#comment-16080129 ]=20 Arina Ielchiieva commented on DRILL-4264: ----------------------------------------- Some useful notes provided by [~Paul.Rogers]: 1. Escape mechanism for dots in names. (See this for how it is done in [JSO= N|https://stackoverflow.com/questions/2577172/how-to-get-json-objects-value= -if-its-name-contains-dots]. Can we support table[=E2=80=9C1.2.3=E2=80=9D] = syntax in Drill?) 2. Dots in column names: Identify the issue (Drill attaches meaning to the = dots.) Research SQL escape characters. How do other products handle this? G= iven that these names come from JSON, can we use Javascript syntax (table[= =E2=80=9C1.2.3=E2=80=9D])? How do we ensure current behavior does not break= ? Experiment to see what works. > Dots in identifier are not escaped correctly > -------------------------------------------- > > Key: DRILL-4264 > URL: https://issues.apache.org/jira/browse/DRILL-4264 > Project: Apache Drill > Issue Type: Bug > Components: Execution - Codegen > Reporter: Alex > Assignee: Volodymyr Vysotskyi > > If you have some json data like this... > {code:javascript} > { > "0.0.1":{ > "version":"0.0.1", > "date_created":"2014-03-15" > }, > "0.1.2":{ > "version":"0.1.2", > "date_created":"2014-05-21" > } > } > {code} > ... there is no way to select any of the rows since their identifiers con= tain dots and when trying to select them, Drill throws the following error: > Error: SYSTEM ERROR: UnsupportedOperationException: Unhandled field refer= ence "0.0.1"; a field reference identifier must not have the form of a qual= ified name > This must be fixed since there are many json data files containing dots i= n some of the keys (e.g. when specifying version numbers etc) -- This message was sent by Atlassian JIRA (v6.4.14#64029)