[
https://issues.apache.org/jira/browse/IGNITE-17816?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17618799#comment-17618799
]
Andrey Mashenkov edited comment on IGNITE-17816 at 10/17/22 10:05 AM:
----------------------------------------------------------------------
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.
Did all of them were ported? How to check this?
was (Author: amashenkov):
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)
