You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@ignite.apache.org by "Dmitry Pavlov (Jira)" <ji...@apache.org> on 2026/05/09 12:28:00 UTC

[jira] [Commented] (IGNITE-21899) [TCBot] Fix for TC Bot with Ignite version 2.16

    [ https://issues.apache.org/jira/browse/IGNITE-21899?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18079676#comment-18079676 ] 

Dmitry Pavlov commented on IGNITE-21899:
----------------------------------------

Feels like this migration already became a small recovery framework 🙂

The current generic recursive deep-scan over all keep-binary cache values is flexible, but inherently fragile for old persistent DBs: broken metadata, unexpected object graphs or stale derived entries easily turn migration into a repair scenario.

Long-term I think a more reliable approach would be:
- migrate only known cache/type schemas where GridIntList is expected;

> [TCBot] Fix for TC Bot with Ignite version 2.16
> -----------------------------------------------
>
>                 Key: IGNITE-21899
>                 URL: https://issues.apache.org/jira/browse/IGNITE-21899
>             Project: Ignite
>          Issue Type: Task
>            Reporter: Oleg Valuyskiy
>            Assignee: Dmitry Pavlov
>            Priority: Major
>              Labels: ise
>         Attachments: serial_errors_log.txt
>
>
> It's impossible to build the project with Apache Ignite 2.16, as GridIntList#clear(), which was removed in the 2.16 version (https://issues.apache.org/jira/browse/IGNITE-20143), is used in TC Bot. All in all, GridIntList is a private API and should not be used in TC Bot.



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