You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Evgeny Stanilovsky (Jira)" <ji...@apache.org> on 2022/12/28 07:30:00 UTC
[jira] [Commented] (IGNITE-18406) Sort out and merge Calcite tickets to Ignite 3.0 (step 8)
[ https://issues.apache.org/jira/browse/IGNITE-18406?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17652404#comment-17652404 ]
Evgeny Stanilovsky commented on IGNITE-18406:
---------------------------------------------
2 issues was implemented under this task :
https://issues.apache.org/jira/browse/IGNITE-18206
> Sort out and merge Calcite tickets to Ignite 3.0 (step 8)
> ---------------------------------------------------------
>
> Key: IGNITE-18406
> URL: https://issues.apache.org/jira/browse/IGNITE-18406
> Project: Ignite
> Issue Type: Task
> Components: sql
> Reporter: Yury Gerzhedovich
> Assignee: Evgeny Stanilovsky
> Priority: Major
> Labels: ignite-3
>
> Let's sort out tikets contains by [filter|https://issues.apache.org/jira/issues/?jql=project%3DIgnite%20and%20labels%20in(calcite3-required)%20and%20labels%20not%20in(calcite2-required)%20order%20by%20resolutiondate%20ASC].
> 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.
> h4.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)