You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Pavel Pereslegin (Jira)" <ji...@apache.org> on 2026/01/23 11:25:00 UTC

[jira] [Assigned] (IGNITE-27648) Sql. Need to synchronize JSON serializator/deserializator with Calcite

     [ https://issues.apache.org/jira/browse/IGNITE-27648?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Pavel Pereslegin reassigned IGNITE-27648:
-----------------------------------------

    Assignee: Pavel Pereslegin

> Sql. Need to synchronize JSON serializator/deserializator with Calcite
> ----------------------------------------------------------------------
>
>                 Key: IGNITE-27648
>                 URL: https://issues.apache.org/jira/browse/IGNITE-27648
>             Project: Ignite
>          Issue Type: Improvement
>          Components: sql ai3
>            Reporter: Iurii Gerzhedovich
>            Assignee: Pavel Pereslegin
>            Priority: Major
>              Labels: ignite-3
>
> Usually, during an upgrade to a new version of Calcite engine, we update most of the classes that we take from Calcite, and make some improvements on our side.
> However, we totally forgot about JSON serialization/deserialization part. It leads to making our own fixes, which usually involve repeats fixes in the original Code, we don't fix other issues and code became tottaly different.
> Let's synchronize this part, need to start fwith RelJson class



--
This message was sent by Atlassian Jira
(v8.20.10#820010)