ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vladimir Ozerov (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (IGNITE-6276) SQL: Investigate parser generators
Date Wed, 06 Sep 2017 13:00:03 GMT

     [ https://issues.apache.org/jira/browse/IGNITE-6276?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Vladimir Ozerov updated IGNITE-6276:
------------------------------------
    Fix Version/s: 2.3

> 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
>             Fix For: 2.3
>
>
> 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)

Mime
View raw message