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

Posted to issues@ignite.apache.org by "Ignite TC Bot (Jira)" <ji...@apache.org> on 2026/02/02 19:04:00 UTC

[jira] [Commented] (IGNITE-27677) Use message serializer for StatusCheckMessage

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

Ignite TC Bot commented on IGNITE-27677:
----------------------------------------

{panel:title=Branch: [pull/12658/head] Base: [master] : No blockers found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/12658/head] Base: [master] : No new tests found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}{panel}
[TeamCity *--&gt; Run :: All* Results|https://ci2.ignite.apache.org/viewLog.html?buildId=8824714&amp;buildTypeId=IgniteTests24Java8_RunAll]

> Use message serializer for StatusCheckMessage
> ---------------------------------------------
>
>                 Key: IGNITE-27677
>                 URL: https://issues.apache.org/jira/browse/IGNITE-27677
>             Project: Ignite
>          Issue Type: Improvement
>            Reporter: Vladimir Steshin
>            Assignee: Vladimir Steshin
>            Priority: Minor
>              Labels: IEP-132, ise
>
> Despite we decided to remove `StatusCheckMessage` in IGNITE-14053, this task is not so simple. But the old serialization blocks support of rolling upgrade. Refactoring message to new serialization looks simple. Meanwhile, we might refactor it.



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