You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@ignite.apache.org by "Yury Gerzhedovich (Jira)" <ji...@apache.org> on 2021/03/12 11:05:00 UTC

[jira] [Updated] (IGNITE-13971) Merge Calcite SQL engine to Ignite 3.0

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

Yury Gerzhedovich updated IGNITE-13971:
---------------------------------------
    Summary: Merge Calcite SQL engine to Ignite 3.0  (was: Merge Calcite SQL engine to master)

> Merge Calcite SQL engine to Ignite 3.0
> --------------------------------------
>
>                 Key: IGNITE-13971
>                 URL: https://issues.apache.org/jira/browse/IGNITE-13971
>             Project: Ignite
>          Issue Type: Improvement
>          Components: sql
>            Reporter: Yury Gerzhedovich
>            Priority: Major
>
> The main goal is start development on a ticket-based approach when we could merge each new ticket to master separately, instead of integration branch approach.  Also the new engine will be available to users to start using and testing it.
> We need to ensure the new SQL engine based on Calcite is not affect the current implementation, discuss it on a dev list and merge it to master branch.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)