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 D664C200D08 for ; Wed, 6 Sep 2017 11:32:07 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id D36D5160CD8; Wed, 6 Sep 2017 09:32: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 2E278161198 for ; Wed, 6 Sep 2017 11:32:07 +0200 (CEST) Received: (qmail 57863 invoked by uid 500); 6 Sep 2017 09:32:06 -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 57849 invoked by uid 99); 6 Sep 2017 09:32:05 -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; Wed, 06 Sep 2017 09:32:05 +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 48FE3CC2C4 for ; Wed, 6 Sep 2017 09:32:05 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -100.002 X-Spam-Level: X-Spam-Status: No, score=-100.002 tagged_above=-999 required=6.31 tests=[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 (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id G2lyllRIR_AP for ; Wed, 6 Sep 2017 09:32: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 D1D9F5FC69 for ; Wed, 6 Sep 2017 09:32: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 678D5E045B for ; Wed, 6 Sep 2017 09:32: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 2308C24147 for ; Wed, 6 Sep 2017 09:32:00 +0000 (UTC) Date: Wed, 6 Sep 2017 09:32:00 +0000 (UTC) From: "Sergey Kalashnikov (JIRA)" To: dev@ignite.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Created] (IGNITE-6276) SQL: Investigate parser generators MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Wed, 06 Sep 2017 09:32:08 -0000 Sergey Kalashnikov created IGNITE-6276: ------------------------------------------ Summary: SQL: Investigate parser generators Key: IGNITE-6276 URL: https://issues.apache.org/jira/browse/IGNITE-6276 Project: Ignite Issue Type: Improvement Components: sql Reporter: Sergey Kalashnikov Assignee: Sergey Kalashnikov Now ignite relies on H2 for SQL processing. It has been discussed many times on dev list that we must start introducing our own SQL core in small incremental steps. Let's start with analyzing the options for implementing the parser part. We may begin with http://www.antlr.org/ and create a simple separate project that would generate the parser for some simple DDL commands like DROP INDEX. This will give us a hint on the complexity and limitations of the approach. 1) Set up Maven/ANTLR. 2) Prepare lexer/parser. 3) Generate. 4) Write a test. -- This message was sent by Atlassian JIRA (v6.4.14#64029)