[jira] [Commented] (IGNITE-17816) Sort out and merge Calcite tickets to Ignite 3.0 (step 7)
[ https://issues.apache.org/jira/browse/IGNITE-17816?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17618920#comment-17618920 ] Andrey Mashenkov commented on IGNITE-17816: --- [~jooger], thanks for your contribution, merged to main. > Sort out and merge Calcite tickets to Ignite 3.0 (step 7) > -- > > Key: IGNITE-17816 > URL: https://issues.apache.org/jira/browse/IGNITE-17816 > Project: Ignite > Issue Type: Improvement > Components: sql >Reporter: Yury Gerzhedovich >Assignee: Yury Gerzhedovich >Priority: Major > Labels: calcite, ignite-3 > Fix For: 3.0.0-beta1 > > Time Spent: 40m > Remaining Estimate: 0h > > Let's merge the following tickets to ignite 3.0: > https://issues.apache.org/jira/browse/IGNITE-16443 > https://issues.apache.org/jira/browse/IGNITE-16151 > https://issues.apache.org/jira/browse/IGNITE-16701 > https://issues.apache.org/jira/browse/IGNITE-16693 > https://issues.apache.org/jira/browse/IGNITE-16053 > After merge needs to remove the label {*}calcite3-required{*}. > Tickets that could be simply merged - merge immediately. For hard cases let's > create separate tickets with estimation and link them to IGNITE-15658 or > links to blocker ticket. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (IGNITE-17816) Sort out and merge Calcite tickets to Ignite 3.0 (step 7)
[ https://issues.apache.org/jira/browse/IGNITE-17816?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17618814#comment-17618814 ] Andrey Mashenkov commented on IGNITE-17816: --- I see 6 tickets in description and 8 commits, all of them have same name. > Sort out and merge Calcite tickets to Ignite 3.0 (step 7) > -- > > Key: IGNITE-17816 > URL: https://issues.apache.org/jira/browse/IGNITE-17816 > Project: Ignite > Issue Type: Improvement > Components: sql >Reporter: Yury Gerzhedovich >Assignee: Yury Gerzhedovich >Priority: Major > Labels: calcite, ignite-3 > Time Spent: 10m > Remaining Estimate: 0h > > Let's merge the following tickets to ignite 3.0: > https://issues.apache.org/jira/browse/IGNITE-16443 > https://issues.apache.org/jira/browse/IGNITE-16151 > https://issues.apache.org/jira/browse/IGNITE-16701 > https://issues.apache.org/jira/browse/IGNITE-16693 > https://issues.apache.org/jira/browse/IGNITE-16053 > After merge needs to remove the label {*}calcite3-required{*}. > Tickets that could be simply merged - merge immediately. For hard cases let's > create separate tickets with estimation and link them to IGNITE-15658 or > links to blocker ticket. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (IGNITE-17816) Sort out and merge Calcite tickets to Ignite 3.0 (step 7)
[ https://issues.apache.org/jira/browse/IGNITE-17816?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17618807#comment-17618807 ] Yury Gerzhedovich commented on IGNITE-17816: [~amashenkov] , yes, all of them are ported ( one has been removed from the scope). Each of them ported as a separate commit, except few additional commits related to fixing flaky reworked test and fixes related to code style. > Sort out and merge Calcite tickets to Ignite 3.0 (step 7) > -- > > Key: IGNITE-17816 > URL: https://issues.apache.org/jira/browse/IGNITE-17816 > Project: Ignite > Issue Type: Improvement > Components: sql >Reporter: Yury Gerzhedovich >Assignee: Yury Gerzhedovich >Priority: Major > Labels: calcite, ignite-3 > Time Spent: 10m > Remaining Estimate: 0h > > Let's merge the following tickets to ignite 3.0: > https://issues.apache.org/jira/browse/IGNITE-16443 > https://issues.apache.org/jira/browse/IGNITE-16151 > https://issues.apache.org/jira/browse/IGNITE-16701 > https://issues.apache.org/jira/browse/IGNITE-16693 > https://issues.apache.org/jira/browse/IGNITE-16053 > After merge needs to remove the label {*}calcite3-required{*}. > Tickets that could be simply merged - merge immediately. For hard cases let's > create separate tickets with estimation and link them to IGNITE-15658 or > links to blocker ticket. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (IGNITE-17816) Sort out and merge Calcite tickets to Ignite 3.0 (step 7)
[ https://issues.apache.org/jira/browse/IGNITE-17816?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17618799#comment-17618799 ] Andrey Mashenkov commented on IGNITE-17816: --- There are 6 tickets in description to port to ignite-3. It is almost impossible to figure out quickly what changes in 40+ files relates to what tickets. > Sort out and merge Calcite tickets to Ignite 3.0 (step 7) > -- > > Key: IGNITE-17816 > URL: https://issues.apache.org/jira/browse/IGNITE-17816 > Project: Ignite > Issue Type: Improvement > Components: sql >Reporter: Yury Gerzhedovich >Assignee: Yury Gerzhedovich >Priority: Major > Labels: calcite, ignite-3 > Time Spent: 10m > Remaining Estimate: 0h > > Let's merge the following tickets to ignite 3.0: > https://issues.apache.org/jira/browse/IGNITE-16443 > https://issues.apache.org/jira/browse/IGNITE-16151 > https://issues.apache.org/jira/browse/IGNITE-16701 > https://issues.apache.org/jira/browse/IGNITE-16693 > https://issues.apache.org/jira/browse/IGNITE-15425 > https://issues.apache.org/jira/browse/IGNITE-16053 > After merge needs to remove the label *calcite3-required*. > Tickets that could be simply merged - merge immediately. For hard cases let's > create separate tickets with estimation and link them to IGNITE-15658 or > links to blocker ticket. -- This message was sent by Atlassian Jira (v8.20.10#820010)