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 2022/10/14 06:55:00 UTC
[jira] [Assigned] (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:all-tabpanel ]
Yury Gerzhedovich reassigned IGNITE-17816:
------------------------------------------
Assignee: Yury Gerzhedovich
> 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)