Mailing-List: contact issues-help@ignite.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@ignite.apache.org
Date: Thu, 17 Mar 2016 14:20:33 +0000 (UTC)
From: "Sergi Vladykin (JIRA)" <jira@apache.org>
To: issues@ignite.apache.org
Message-ID: <JIRA.12951061.1458178385000.48689.1458224433848@Atlassian.JIRA>
In-Reply-To: <JIRA.12951061.1458178385000@Atlassian.JIRA>
References: <JIRA.12951061.1458178385000@Atlassian.JIRA>
 <JIRA.12951061.1458178385865@arcas>
Subject: [jira] [Commented] (IGNITE-2855) Apache Calcite as an SQL query
 parser and optimizer
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/IGNITE-2855?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15199590#comment-15199590 ] 

Sergi Vladykin commented on IGNITE-2855:
----------------------------------------

I don't think it's worth trying to integrate this fancy thing in ignite (in near future at least). But may be it makes sense to do some experimenting in independent integration project and evaluate what it can give us.

> Apache Calcite as an SQL query parser and optimizer
> ---------------------------------------------------
>
>                 Key: IGNITE-2855
>                 URL: https://issues.apache.org/jira/browse/IGNITE-2855
>             Project: Ignite
>          Issue Type: New Feature
>            Reporter: Roman Shtykh
>
> Apache Calcite (https://calcite.apache.org/) can be used as an SQL query parser, validator and optimizer with Ignite at the back end.


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)