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/04/15 13:28:00 UTC

[jira] [Commented] (IGNITE-28308) Remove Serializable from discovery custom messages.

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

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

{panel:title=Branch: [pull/13001/head] Base: [master] : No blockers found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/13001/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=9006431&amp;buildTypeId=IgniteTests24Java8_RunAll]

> Remove Serializable from discovery custom messages.
> ---------------------------------------------------
>
>                 Key: IGNITE-28308
>                 URL: https://issues.apache.org/jira/browse/IGNITE-28308
>             Project: Ignite
>          Issue Type: Task
>            Reporter: Nikita Amelchev
>            Assignee: Nikita Amelchev
>            Priority: Minor
>              Labels: IEP-132, important, ise
>             Fix For: 2.19
>
>          Time Spent: 2h 20m
>  Remaining Estimate: 0h
>
> To fully migrate to the new serialization framework, we need to remove Serializable from the DiscoverySpiCustomMessage interface in order to avoid supporting two types of serialization.



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