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

Posted to issues@ignite.apache.org by "Mikhail Petrov (Jira)" <ji...@apache.org> on 2026/09/01 08:00:00 UTC

[jira] [Updated] (IGNITE-28851) Embed Ignite Features to Serialization Mechanism for transport betwwen Ignite nodes

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

Mikhail Petrov updated IGNITE-28851:
------------------------------------
    Summary: Embed Ignite Features to Serialization Mechanism for transport betwwen Ignite nodes  (was: Embeded Ignite Features to Serialization Mechanism for transport betwwen Ignite nodes)

> Embed Ignite Features to Serialization Mechanism for transport betwwen Ignite nodes
> -----------------------------------------------------------------------------------
>
>                 Key: IGNITE-28851
>                 URL: https://issues.apache.org/jira/browse/IGNITE-28851
>             Project: Ignite
>          Issue Type: Task
>            Reporter: Mikhail Petrov
>            Assignee: Mikhail Petrov
>            Priority: Major
>              Labels: IEP-132, ise
>             Fix For: 2.19
>
>          Time Spent: 1h 50m
>  Remaining Estimate: 0h
>
> The main goal of this ticket is to provide a mechanism that guarantees the same serialization order of message fields across nodes running different Ignite versions, both while a Rolling Upgrade is in progress and after it has been completed.
> To achieve symmetric serialization behavior across nodes, the serialization process should use the node's local feature set and the active cluster feature set.



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