[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 ] Aleksey Plekhanov updated IGNITE-13971: --- Labels: calcite ignite-3 (was: ignite-3) > 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 >Assignee: Konstantin Orlov >Priority: Major > Labels: calcite, ignite-3 > > 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 integrated and available for users to > start using and testing it. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[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 ] Aleksey Plekhanov updated IGNITE-13971: --- Labels: ignite-3 (was: calcite2-required calcite3-required ignite-3) > 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 >Assignee: Konstantin Orlov >Priority: Major > Labels: ignite-3 > > 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 integrated and available for users to > start using and testing it. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[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: --- Labels: calcite2-required calcite3-required ignite-3 (was: calcite2-required calcite3-required) > 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 >Assignee: Konstantin Orlov >Priority: Major > Labels: calcite2-required, calcite3-required, ignite-3 > > 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 integrated and available for users to > start using and testing it. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[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: --- Labels: calcite2-required calcite3-required (was: ) > 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 > Labels: calcite2-required, calcite3-required > > 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 integrated and available for users to > start using and testing it. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[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: --- Description: 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 integrated and available for users to start using and testing it. was: 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. > 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 integrated and available for users to > start using and testing it. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[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)
